Previous Topic: OLOG - OPERLOGONext Topic: OUTC - OUTCLASS and OUTP - OUTPUT


OSSR - OS Services

OSSR001E GETMAIN failed for work area

The request for storage of the OS services module cannot find enough available storage. Try increasing the region size of the application where SYSVIEW is running. If this error occurs repeatedly, contact CA Technical Support.

OSSR002E Invalid function code - <code>

The request made to the OS services module contains the invalid function code <code>. Note the function code and the circumstances in which the error occurred. Contact CA Technical Support.

OSSR003E Invalid subfunction code - <code>

The request made to the OS services module contains an invalid subfunction code <code>. Note the code and the circumstances in which the error occurred. Contact CA Technical Support.

OSSR005E OS services module abended <code>

The OS services module has abended while processing a request. <code> is an abend code. If this message is received while trying to copy output to a data set, a new copy data set with a larger allocation must be specified in the GENERAL section of the profile.

For more information, issue the STATUS command, print the contents of the entire display (PRINT ALL), and then contact CA Technical Support.

OSSR020E Maximum number of datasets open

The request made to the OS services module to access a data set has failed to find data set areas available. Note the circumstances in which this error occurred.

Contact CA Technical Support.

OSSR021E Open failed for dataset <dataset-name>

The attempt to open data set <dataset-name> has failed. Note the circumstances in which this error occurred.

Contact CA Technical Support.

OSSR022E I/O buffer not available

The attempt to get an I/O buffer for a data set has failed. Try ending your session and starting a new one. If this error occurs repeatedly, contact CA Technical Support.

OSSR023E File or member was empty - <xxxxxxxxxxxxxxxxx>

The attempt to read file or member <xxxxxxxxxxxxxxxxx> has failed because the file is empty. Note the circumstances in which this error occurred.

Contact CA Technical Support.

OSSR024E Member <memname> not found

The attempt to read member <memname> from a partitioned data set has failed because the member cannot be found. Note the circumstances in which this error occurred.

Contact CA Technical Support.

OSSR025E Allocation failed for dataset <dsname> - RC= <code>

The attempt to dynamically allocate data set <dsname> has failed. <code> is the return code from dynamic allocation. For a definition of the return code, see the SVC 99 Return Codes section in the IBM manual System Macros and Facilities Volume 1 (GC28-1150) for MVS/XA, or Job Management (GC28-1303) for MVS/SP. If the data set name is the help, profile, or security data set name of this product, make sure the data set is cataloged properly.

For more information, note the return code and the circumstances in which the error occurred. Contact CA Technical Support.

OSSR027E File <ddname> not found

A request was made to close file <ddname> but the file could not be found. Note the circumstances in which the error occurred and contact CA Technical Support.

OSSR028E Profile dataset is in use and could not be allocated

The profile data set is being updated or compressed and cannot be allocated. If you receive this message when starting your session, a default profile is used. If you receive this message when trying to update your profile, try the update again later.

OSSR029E I/O error <oper> block <blk>

An I/O error occurred reading or writing a block of data from the output index data set. Contact CA Technical Support.

OSSR030E Find for member <xxxxxxxx> failed - RC=<xxxxxxxx>

The FIND macro failed while trying to locate member <xxxxxxxx>. Note the return code and the circumstances in which the message occurred. Contact CA Technical Support.

OSSR031W Deallocation failed for DDname <ddname> - RC=<rc>

A request was made to deallocate file <ddname> but the request failed with return code <rc>. Note the circumstances in which the error occurred. Contact CA Technical Support.

OSSR032E Dataset is partitioned - <dataset>

An attempt was made to process a sequential data set, but the data set was found to be a partitioned data set. The data set will not be used for sequential processing.

OSSR033E Dataset is not partitioned - <dataset>

An attempt was made to process a partitioned data set, but the data set was found to not be a partitioned data set. The data set will not be used for partitioned processing.

OSSR034E <synadaf i/o error message 1>

An I/O error has occurred. The text of this message is generated by the IBM SYNADAF macro.

OSSR035E <synadaf i/o error message 2>

An I/O error has occurred. The text of this message is generated by the IBM SYNADAF macro.

OSSR036E I/O error updating profile member @<8> in place

An I/O error occurred attemping to update a profile member in place. Contact CA Technical Support.