xcli messages

This section details the messages that might be produced by xcli and explains what they mean.

Incorrect syntax in configuration file.

In-Flight Trace has found syntax that it cannot parse in the configuration file. Check the syntax carefully with the information in this manual. Correct the error and rerun the command.

Cannot create the semaphore '%d', error %ld.

The error message is from the operating system. There might be a memory usage problem which requires an operating system reboot.

Cannot lock the semaphore, error %ld.

The error message is from the operating system. There might be a memory usage problem which requires an operating system reboot.

Cannot create the shared memory, error %ld.

The error message is from the operating system. There might be a memory usage problem which requires an operating system reboot.

Cannot map the shared memory, error %ld.

The error message is from the operating system. There might be a memory usage problem which requires an operating system reboot.

Incorrect value for key %s in section '%s'.

The syntax of the configuration file is correct but the indicated key in the indicated section has an incorrect value.

The tracing facility is not active.

If the "Enable" key in the [_GLOBAL_] section is set to "n", the tracing facility is disabled. To enable it, edit the configuration file, set the "Enable" key in the [_GLOBAL_] section to "y", save the file and restart IBM Workload Scheduler.

Unable to open file '%s', error %d.

The error message is from the operating system. Check the error code. The file might be open in another process, or the user running the command might not have rights to open the file. Correct the problem and try the command again.

Not enough free memory to allocate %d bytes.

The message indicates the memory required by your configuration. Either reduce the amount of memory used by the configuration by editing the configuration file, changing the values, saving the file and restarting IBM Workload Scheduler, or free some memory by closing other applications. You might also be able to enlarge the memory paging file. Use the -config option to reinitialize the memory.

Unable to write to file '%s', error %d.

The error message is from the operating system. Check the error code. The file might have been deleted by another process, or the user running the command might not have rights to write to the file. Correct the problem and try the command again.

Unable to read from file '%s', error %d.

The error message is from the operating system. Check the error code. The file might have been deleted by another process, or the user running the command might not have rights to read from the file. Correct the problem and try the command again.

The selected file does not contain a valid snapshot.

You have identified a snapshot file to format, but either it is not a snapshot file or the snapshot file was not written correctly. Check the name you supplied. If it was not correct, reissue the command with the correct file name. If the file name is correct, rerun the snap to regenerate the file.

Memory not correctly initialized.

The shared memory has not been correctly created. Check that there is sufficient free memory to create the shared memory you have defined in the configuration file.

The tracing facility is not active for program %s.

You have requested to change tracing information for the indicated program which is not active. Activate the program first, using the -active option.

The tracing facility is not active for segment %s.

You have requested to change tracing information for the indicated segment which is not active. Activate the segment first, using the -active option.

Operation successful.

No-brainer! Whatever you were doing has worked!

Unable to remove the semaphore %x, error %d.

The error message is from the operating system. There might be a memory usage problem which requires an operating system reboot.

Unable to remove the shared memory %x, error %d.

The error message is from the operating system. There might be a memory usage problem which requires an operating system reboot.

The tracing facility is not active for product %s.

You have identified a product for which the "Enable" key in the [_GLOBAL_] section is set to "n", and so the tracing facility is disabled. To enable it, edit the appropriate configuration file, setting the "Enable" key in the [_GLOBAL_] section to "y", save the file and restart the product.

The maximum number of products (%d) has already been reached.

In-Flight Trace can only trace a limited number of products at one time, regardless of the amount of memory available. You have reached that limit!

The sections '%s' and '%s' have the same segment number but different %s.

Some of the keys in a section are "segment-based", in that if more than one section traces to the same segment, they must have the same values. For example, the filter file for programs that trace to the same segment must be the same. Either change the programs to trace to different segments or supply the same filter file for all programs that trace to the same segment.

Segment %d is too small for the filter file '%s'.

The space you allocate to a segment is used to store the filter file for more than 12,000 functions, in addition to the traces. In this case, you have not created sufficient space to store the filter file. You cannot change the size of the filter file, because it uses one entry for every function in the product, regardless of whether that function is or is not filtered for tracing. So you must increase the segment size by editing the configuration file, saving it and restarting IBM Workload Scheduler.

Cannot open the symbols database '%s'.

Either the symbols database does not exist with the name you supplied, the user running the command does not have the rights to open the file, or the file is corrupted. Check that the name is correct and ensure that you are the TWS_user.

Too many input parameters.

The syntax of the command you supplied is not correct. Check the syntax with what is documented in this publication and try the command again.

An error occurred while opening the symbols database '%s'.

The database file might be corrupted.

Warning: the function ID %d is not in the symbols database.

You have tried to add or remove a function which is not in the symbols database. Check the source from which you obtained the function name or ID. Check that you are using the correct symbols database. The default symbols database is xdb.dat. Correct the error and try the command again.

Duplicated section '%s' in the configuration file.

Each program section can only be present once in the configuration file. Perhaps you copied a section intending to change the name but did not. Edit the configuration file, save it and restart IBM Workload Scheduler.

Warning: There is a mismatch between the size of the new filter file and the previous one (new size = %d, previous size = %d).

You have used the -filter option to supply a new filter file, but the new filter file was generated using a symbols database different from that used when the filter file currently in use was created. Put a different way, you seem to have used different symbols databases to create two different filter files, and the two different databases have different numbers of functions. In-Flight Trace can continue tracing but the filtering might not be applied correctly. You are advised always to use only the symbols database generated when the version of the product you are tracing was built.

Cannot clean up the shared memory because some process is currently using it.

You have used the -clean option to clean the shared memory, but one or more processes is still using the shared memory, so it cannot be cleaned. Use your system resources to determine which process is using the shared memory, stop it, and retry the -clean option.