IMS$ - IMS Messages

Messages and Descriptions › All -I- Messages › IMS$ - IMS Messages

IMS$ - IMS Messages

IMS$002E <service> failed, <reason>

Attempted service call failed for indicated reason.

IMS$003E No IMS subsystems found

No IMS subsystems were found on the MVS image where the current command was issued.

IMS$004E No active IMS control region found

No active IMS control regions were found on the MVS image where the current command was issued.

IMS$005I Line command <command> not yet implemented

The indicated line command is planned or under development but is not yet fully functional.

IMS$006E IMS control region <subsys> not <reason>

The IMS control region for the indicated subsystem is not in a valid status for the attempted command or is not authorized.

IMS$007I Switched to IMS control region <subsys> ASID <asid>

The specified IMS control region is now the current target ASID.

IMS$008W IMS control region not active in ASID <asid> job <jobname>

The control region is not active in ASID with jobname.

IMS$009E <command> line command invalid for status <status>

Attempted line command is not valid for the indicated status.

IMS$010E <text> failed, rc <rc> rs <reason>

The indicated service failed for rc and reason.

IMS$011E <text>

Informational only.

IMS$012E Invalid < > < > < > parameter - < >

Informational only.

IMS$013W No output found for <jobnm>

No output could be found for the specified jobname.

IMS$014W No authorized output found for <jobnm>

No output could be found for the specified jobname due to security authorization.

IMS$015E Invalid <command> command syntax - <text>

Invalid command syntax for the indicated command. The text field contains the original command string.

IMS$016I Command <text> IMSid <imsid> - <command>

A command has been sent to IMS for processing.

<text>- Submitted to Accepted by
<imsid>- IMS subsystem ID
<command> - Command string

IMS$017E Unable to determine outstanding WTOR reply id for imsid <imsid>

Attempted IMS command to the indicated imsid but no WTOR could be found for the command to be issued.

IMS$018I Commands will be submitted to IMSid <imsid> ASID <asid> job <job>

Subsequent IMS commands will be issued to the indicated imsid with ASID and job.

IMS$019I <command> line command invalid for <resource>, not <status>

Attempted line command for the indicated resource is not valid because the resource is already in the desired state.

IMS$020I <command> line command invalid for <resource>, already <status>

Attempted line command for the indicated resource is not valid because the resource is already in the desired state.

IMS$021I < > commands < > IMSid <imsid>

Informational only.

IMS$022W Locate IMSid <imsid> WTOR reply id failed, waiting <seconds> for retry <count> of <limit>

An attempt to issue an IMS command to the indicated imsid failed because the WTOR reply ID could not be determined. The command will be retried after the indicated seconds for a count up to the limit number of retries.

IMS$023I <cmd> line command invalid for non-XRF system

The line command issued is not valid for a non-XRF system.

IMS$024E <command> command not supported at IMS <release>

The command is not supported at the specified IMS release.

IMS$025E <command> command invalid for type <regiontype>

The specified command is not valid for the selected region type.

IMS$026I No map defined for selected log record type.

The specified log record type does not have a map defined. This is an informational only message.

IMS$027I <imsid> - IMLB purged for transaction <trancode> UOW=<uow>

The specified IMLB has been purged because the time limit specified on the IMSLOGR-IMLB-PURGE-INTERVAL was exceeded. This event is triggered by the following command:

F SYSVIEW,MODIFY IMSDATA,PURGEIMLB

For more information see the IMSLOGR-IMLB-PURGE-INTERVAL IMSLOGR PARMLIB option and SCHDIMLB PARMLIB member.

IMS$028E <func> error, rc <rtncd> rsn <rsncd>, <text>

For more information regarding the information contained within this message see the IMS Common Services Layer Guide and Reference manual or the IMS Command Reference.

IMS$029I IMS <imsid> - IMLB purge count: <count>

This message indicates that SYSVIEW has purge transaction IMLB that have not terminated by the specified time interval. These transactions will be written to the transaction history log as type Z transactions.

For more information see the IMSLOGR-IMLB-PURGE-INTERVAL IMSLOGR PARMLIB option and SCHDIMLB PARMLIB member.

IMS$030I Shared queues block initialized. SQGroup=<Shared Q group name>

The shared queues group block for the specified IMS shared queues group has been initialized. The shared queues group block contains information related to the queues managed by the Common Queue Server for the named shared queues group.

IMS$031E <imsid> is not configured for shared message queues

The selected IMS is not configured to use shared message queues or is not a member of a shared queues group.

IMS$032I CQS registration successful. Client=<client name> CQS jobname=<CQS jobname> SQGroup=<shared Q group name>

SYSVIEW has successfully registered with the CQS server API managing the queue structures used by the specified shared Q group.

IMS$033I CQS registration terminated. Client=<client name> CQS name= <CQS jobname> SQGroup=<shared Q group name>

SYSVIEW has successfully terminated registration with the CQS server API that is managing the queue structures used by the specified shared Q group.

IMS$034I CQS <structure type> structure connection successful. Primary=<primary structure name> Overflow=<overflow structure name> SQGroup=<shared Q group name>

SYSVIEW has successfully connected to named message queue structures for the specified shared Q group.

IMS$035I CQS <structure type> structure connection terminated. Primary=<primary structure name> Overflow=<overflow structure name> SQGroup=<shared Q group name>

SYSVIEW has successfully terminated the connection to named message queue structures for the specified shared Q group.

IMS$036W CQS server has terminated. CQS jobname=<CQS jobname> SQGroup=<Shared Q group name>

The CQS address space associated with the specified shared queue group has terminated. The SYSVIEW client can no longer process CQS requests for the specified server.

IMS$038W CQS server starting. CQS jobname=<CQS jobname> SQGroup=<Shared Q group name>

The SYSVIEW CQS Event Exit has determined that the specified CQS address space is starting. The SYSVIEW client will reconnect prior to issuing CQS requests.

IMS$039W CQS server terminating. CQS jobname=<CQS jobname> SQGroup=<Shared Q group name>

The SYSVIEW CQS Event Exit has determined that the specified CQS address space is terminating. The SYSVIEW client can no longer process CQS requests for the specified CQS server.

IMS$040W CQS address space is inactive. CQS jobname=<CQS jobname> SQGroup=<Shared Q group name>

The request failed because the target CQS address space is inactive. The SYSVIEW client can no longer process requests for the CQS address space.

IMS$041E IMS <imsid> is not a using shared <Q type> queues

The request failed because the target IMS is not using shared Msg or shared Emh queues.

IMS$042E The IMSCQS task is unable to locate the target SQ Group Block. SQGroup=<Shared Q group name> CQS id=<CQS ssid>

The request failed because SYSVIEW was unable to locate the SQ Group block for the target group. The CQS address space may have terminated or never started.

IMS$043E The CQS Server address space is inactive for IMS <imsid>

The IMS subsystem was determined to be using shared queues, however the CQS Server address space associated with the subsystem is inactive at this time.

IMS$044W The IMSCQS task is unable to register with the CQS API. SQGroup=<Shared Q group name> CQS id=<CQS ssid>

The IMSCQS task is not registered with the specified CQS subsystem API. We are unable to retrieve statistics at this time.

IMS$045W The IMSCQS task is unable to connect to the message structure. SQGroup=<Shared Q group name> CQS id=<CQS ssid>

The IMSCQS task is not connected to the specified CQS subsystem message structures. We are unable to retrieve statistics at this time.

IMS$046I The shared queues group block has been purged. SQGroup=@<8> CQS ssid=@<4>

The shared queue group block associated with the indicated shared queues group has been purged. This is the result of the MODIFY IMSCQS,PURGE command.

IMS$048I Previous Resource Manager disabled

The IMS Resource Manager associated with the previous IMS Logger environment has been disabled. A new one will be defined.

IMS$049E < > parameter required for < > < > command

Informational only.

IMS$050E Field name < > ambiguous - Specify more chars for exact match

Informational only.

IMS$051E Field name < > not found

Informational only.

IMS$052E Invalid < > keyword, max len is 12 - <text>

Informational only.

IMS$053E Invalid < > keyword value - <text>

Informational only.

IMS$054E Invalid < > value, max len is 9 - <text>

Informational only.

IMS$055E Invalid < > value, non-numeric chars found - <text>

Informational only.

IMS$056E Invalid < > value, less than min of < > - <text>

Informational only.

IMS$057E Invalid < > value, greater than max of < > - <text>

Informational only.

IMS$058E Invalid < > value, len less than min of < > - <text>

Informational only.

IMS$059E Invalid < > value, len greater than max of < > - <text>

Informational only.

IMS$060E Invalid < > value, string contains invalid chars - <text>

Informational only.

IMS$061E Invalid < > value, 1st char in string is invalid - <text>

Informational only.

IMS$062E Invalid < > value, <text> - <text>

Informational only.

IMS$063E Unable to obtain IMS region info - <text>

The IMS region information was unable to be obtained. The <text> field describes the reason for the failure. This error indicates a possible unsupported IMS configuration. Contact CA Technical Support.

IMS$064E Invalid input - <input>. Enter <option> to turn <action> the Osam GTF trace

The option selected for the OSAM GTF trace input field in the info area of the IMSOSAM display is invalid.

Valid options are:

ACTIVE - Turn on the trace if the current state is inactive.
INACTIVE - Turn off the trace if the current state is active.

IMS$065E Invalid input specified for <option> - <value>

The value specified for the PI trace option selected is invalid. For a list of valid keywords, review the help for the IMSPI command or see the IMS /TRACE command documentation in the IMS Commands Reference Manual.

IMS$066E <trctype> trace not active

The indicated trace must be activated.

IMS$068W The IMS subsystem that owns the target database is no longer the target asid of the current command.

Return to the IMSDBASE display or switch to the correct target IMS subsystem.

IMS$070I Enter <command> command with a valid option

The option selected for the indicated command is invalid.

IMS$071W Line command <command> invalid for <option> option

The line command is invalid on the line selected. The command is valid for the APDB and REGN options only.

IMS$072E Invalid input - <input>. Enter <value> to turn <action> the DC Monitor trace

Invalid input specified. See the message text for possible input values.

IMS$080I Information only

This message specifies information related to commands passed to the DBRC API.

IMS$081E IMS id parm required for <command>

A required parameter was not supplied for the indicated command.

IMS$082E IMS region type <rtype> not valid for TLOG line command

The TLOG line command is only valid for IMS dependent regions.

IMS$084E Region not scheduled

The selected region is not currently scheduled.

IMS$085E Region type not MPP, BMP or FP

The selected region is not an MPP, BMP or Fast Path region.

IMS$086W IMS control region <imsid> not supported at release <release>

The selected region is at a release level which is no longer supported.

IMS$087W IMS logger dataspace cell pool shortage for IMS <imsid>

Storage used to monitor IMS batch or message regions is unavailable. Region and transaction monitoring may become unavailable until storage becomes available.

IMS$088W IMS logger transaction max event exceeded for IMS <imsid>

A transaction has exceeded the maximum number of events monitored as specified by the IMSLOGR PARMLIB option TRAN-EVENT-MAX-MONITORED. Subsequent events beyond this limit are not reported.

IMS$089E IMS <imsid> Logger dataspace initialization failed - <reason>

The IMS Logger dataspace failed to initialize because the dataspace size is too small. Increase the storage by incrementing the value specified on the TRAN-DATASPACE-SIZE IMSLOGR PARMLIB option.

IMS$090E IMS <imsid> OTMA GRNAME not found or not specified

The IMS OTMA XCF group name was not found or not specified in the IMS DFSPBxxx member.