Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the "IMS-MESSAGE-TRACE" option is set to "YES" in the IMSDATA parmlib member.
Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the "IMS-MESSAGE-TRACE" option is set to "YES" in the IMSDATA parmlib member.
Reserved
Reserved
Reserved
Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the "IMS-MESSAGE-TRACE" option is set to "YES" in the IMSDATA parmlib member.
Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the IMS-MESSAGE-TRACE option is set to YES in the IMSDATA parmlib member.
Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the IMS-MESSAGE-TRACE option is set to YES in the IMSDATA parmlib member.
Reserved
Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the IMS-MESSAGE-TRACE option is set to YES in the IMSDATA parmlib member.
Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the IMS-MESSAGE-TRACE option is set to YES in the IMSDATA parmlib member.
Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the IMS-MESSAGE-TRACE option is set to YES in the IMSDATA parmlib member.
Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the IMS-MESSAGE-TRACE option is set to YES in the IMSDATA parmlib member.
Diagnostic informational only. This message is written to the console from the IMS Logger Resource Manager when the IMS-MESSAGE-TRACE option is set to YES in the IMSDATA parmlib member.
Reserved
Reserved
Reserved
Reserved
An error has occurred when attempting to install the IMS hook intercept specified by <hookid>. Contact CA Technical Support.
An error has occurred when attempting to activate the IMS hook intercept specified by <hookid>. The intercept was found not to be installed and could not be activated Contact CA Technical Support.
An error has occurred when attempting to activate the IMS hook intercept specified by <hookid>. Contact CA Technical Support.
An error has occurred when attempting to de-activate the IMS hook intercept specified by <hookid>. Contact CA Technical Support.
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
An IMS TRACE SET MONITOR command has been entered. The Monitor Trace Command Pre-processing intercept has detected this and has temporarily de-activated the Monitor DC Monitor intercept until the trace command completes. This is an informational only message.
An IMS TRACE SET MONITOR command has been entered. The Monitor Trace Command preprocessing intercept has determined that a trace command was already in progress. This is an informational only message.
An IMS TRACE SET MONITOR command has un-successfully completed. The Monitor Trace Command Post-processing intercept has re-activated the Monitor DC Monitor intercept. This is an informational only message.
An IMS TRACE SET MONITOR command has un-successfully completed. The Monitor Trace Command Post processing intercept has re-activated the Monitor DC Monitor intercept. This is an informational only message.
Reserved
Reserved
Reserved
Reserved
Reserved
An IMS TRACE SET MONITOR command has successfully completed. The Monitor DC Monitor Initialization/Termination intercept has been entered. This is an informational only message.
An IMS TRACE SET MONITOR command has completed processing. The Monitor DC Monitor intercept has been re-activated. This is an informational only message.
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
An error occurred obtaining storage during hook IMS logger intercept installation. Contact CA Technical Support.
An error occurred loading an IMS module during hook IMS logger intercept installation. Contact CA Technical Support.
An error occurred locating the Trace command verb entry during IMS logger intercept installation. Contact CA Technical Support.
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
A failure occurred while processing in an IMS intercept. Recovery Termination Management is invoked and a SDUMP is taken. Intercept processing is disabled immediately and the Monitor Logger task for the IMS Control region is terminated to prevent any further failures. Contact CA Technical Support.
Informational only.
Informational only.
The <name> <type> requires the <parmname> parameter.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
An invalid SSID specification was found. The SSID for the application interface should be specified as:
(ssid)
The SSID must be 4 characters long. The first character must be uppercase alphabetic or national and the second second through fourth must uppercase alphabetic, national, or numeric. Blanks are not allowed between the parentheses and the ssid.
An invalid XPPB_Type code was supplied. This is a should-not-occur error. Contact CA Technical Support.
The SSID <ssid> was successfully extracted from the supplied exec parm.
No SSID was found in the exec parm.
An invalid SSID specification was found. The SSID should be specified as an EXEC card PARM= string as:
EXEC PGM=xxx,PARM='<xxx,xxx,..,>SSID=ssid<,xxx,xxx,...>'
The ssid must be 4 characters long. The first character must be uppercase alphabetic or national and the second second through fourth must uppercase alphabetic, national, or numeric.
An invalid SSID specification was found. The SSID should be specified as an EXEC card PARM= string as
EXEC PGM=xxx,PARM='ssid<,...>'
The ssid must be 4 characters long. The first character must be uppercase alphabetic or national and the second second through fourth must uppercase alphabetic, national, or numeric.
Informational only.
Informational only.
An invalid SSID specification was found. The SSID should be specified as the member name of a data set allocated to the ddname <ddn>:
//<ddn> DD DSN=<dsn>(<ssid>)
The ssid must be 4 characters long. The first character must be uppercase alphabetic or national and the second second through fourth must uppercase alphabetic, national, or numeric.
The SSID <ssid> was successfully extracted from the member name specified on the ddname <ddn> allocation.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
A request to write checkpoint data has been bypassed.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Your password or passphrase was successfully changed.
Informational only.
Informational only.
Informational only.
The user ID validation call to SAF was made using a password phrase instead of a password.
Informational only.
Allocation of G-PVT storage (storage above the 2G bar) completed successfully.
Allocation of G-PVT storage (storage above the 2G bar) failed.
The G-PVT storage limit (storage above the 2G bar) has been increased from <oldlim> to <newlim>.
A request to obtain G-PVT storage (storage above the 2G bar) from the SYSVIEW G-PVT storage manager failed.
A request to release G-PVT storage (storage above the 2G bar) from the SYSVIEW G-PVT storage manager failed.
The request for G-PVT storage (storage above the 2G bar) The SYSVIEW session is terminated. Increase the MEMLIMIT of the application where SYSVIEW is running. The routine name <rtn>, offset <offs>, and length of storage requested are also displayed in the message.
An external API initialization call was requested for the address space represented by <asid> and <ascb> for the task represented by <tcb> and <rb>.
An external API connection call was requested for <userid>.
An external API connection call was requested for <userid> and has been successfully established.
Originating CCI identifier for the external API connection request.
Destination CCI identifier for the external API connection request.
Session CCI identifier for the external API connection or disconnect call.
An external API disconnect call was requested for <userid>.
The external server returned message <text>.
A signal handler for <type> could not be established. Failures of <type> will not be recovered.
A signal handler recovered an exception. The <function> will exit with errors.
An external API request was made but the maximum number of active requests <maxhandles> for the connection has already been reached.
A storage allocation request has failed.
An external API connection call was requested for <userid> and has failed.
An required buffer was not supplied for the GET request.
A buffer of size <size1> was passed to the GET request and is too small. A buffer of size <size2> or larger is required. Reissue the request with a sufficiently sized buffer.
A GET request for column information could not be satisfied because there is no column information for this request.
A CCI error has occurred.
An unexpected error has occurred in the communications module.
Signal <signal> was raised and caught by the signal handler.
Signal SIGABND <abend> was caught by the signal handler.
Informational only.
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
An application identified by <ident> is initializing the Java interface.
An internal logic error has occurred. A request property <propertyid> could not be returned because the request block from the request is not valid.
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Informational only.
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Informational only.
Data collection has been disabled for the specified option.
The request for CSM information has failed. Review prior error messages.
The collection of CSM data is controlled by the option MONITOR-CSM in the parmlib member TCPDATA.
A common reason for failure is the lack of required security authorizations. The user ID making the request must have access to one of the following security resources:
1 - Superuser authority - UID=0
2 - Class : FACILITY
Entity: BPX.SUPERUSER
Access: READ
3 - Class : SERVAUTH
Entity: IST.NETMGMT.sysname.SNAMGMT
Access: READ
The requested action has failed because the user does not have SYSVIEW administrator authority
An action has been taken for the specified data collection request.
A request has been made for the specified data collection type. The type specified is invalid.
A request has been made to set the interval value for the specified data collection type. The interval value specified is invalid.
A request has been made to reset the status of all metrics for the specified data collection type. A reset cannot be performed while the collection for the type is active.
A request has been made to reset the status of all metrics for the specified data collection type.
A request metric was not found.
No data collection monitoring definitions were found to the data collection process specified by the event scheduling function. The data collection process will run, but no data will be collected.
The exception definition contains invalid statements or keywords.
An attempt was made to define or change an exception definition. The reason for failure is included.
Internal debugging message. Contact CA Technical Support for more information if this message is displayed.
A coupling facility request has failed.
Informational only.
A subsystem interface call to obtain information from JES subsystem <jes> failed. <name> is the name of the subsystem call that failed, <rc> is the return code from the SSOB, <rs> is the reason code, if any, from the <name> function and <rs2> is the second reason code, if any.
A JES configuration module for system <sys> could not be found. Assemble a configuration module using the JES libraries for the current system and update the JES PARMLIB member.
The JES configuration module <modname> is not a valid configuration module. Configuration modules must be reassembled with the macro library of the current release. Do not use configuration modules from a previous release.
JES service level <jl> does not match the JES configuration module service level <cl>. Either maintenance has been applied to JES and the configuration module <mod> was not reassembled or the wrong libraries were used to assemble the configuration module. Reassemble the JES configuration module using the libraries that match the JES maintenance applied to the current system.
The version of JES [assign the version number for your book] is an unsupported JES version. Consult the Release Guide for supported JES versions.
The command entered requires information from JES, but JES is not active. Issue the command again when JES is active.
The JES routines attempted to get storage but there was not enough storage to satisfy the request. <name> is the name for the area that could not be acquired and <rtn> is the name of the routine that tried to get the storage. Increase the region size for the address space and retry the request.
An attempt was made to look at a JES control block, but the ID in the control block was invalid. The control block will not be used.
The required services were not available to initialize for the JES subsystem <subsys>.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
The JOBS task was either started with the COLD parameter or a modify command with the COLD parameter was issued. The JOBS task has initiated the cold start.
When processing the JES PARMLIB member, a line did not contain all of the necessary parameters. Check the JES PARMLIB member for documentation about the required parameters.
When processing the JES PARMLIB member, one of the parameters was invalid. Check the JES PARMLIB member for documentation about the required parameters and their format.
The line command entered is not supported for JES subsystem <jes>.
The attempted function <function> <subfunction> is not available for JES subsystem <jes> at this time.
A call was made for JES services but JES services were not available.
Multiple errors occurred while reading data from the JES spool. The subtask terminated and will not restart. Correct the problem with the JES spool and restart the subtask.
The command entered is not available for a JES3 system.
An error occurred while reading data for the <ddname> data set. The most likely cause of this error is the dataset was purged. The error indicated there was an I/O error reading spool.
The line command <linecmd> is invalid for a nonheld job. Clear the line command to continue.
The line command <linecmd> is invalid for a held job. Clear the line command to continue.
The command entered is not available for a JES2 system.
The WTOR option is no longer available. Use the WTOR command to view WTORs.
The command entered is not available for the current JES release.
The action <action> for the JES data set <dsname> failed with return code <rc> and reason code <rsn>.
The action <action> for the JES data set <dsname> abended with abend code <abendcode>.
The status of job <jobname> or a job's data set has changed. The <ddname> variable will be the DD name of the job's data set. Issue the REFRESH subcommand to update the display, or clear the line command to continue.
An invalid spool volume was specified. Use the SPOOLS command to list all valid spool volume names.
There were no output data sets for the selected job. If the job selected is a transaction job, then it has not created any output data sets. Otherwise, the job might have created some output data sets but they have been deleted or requeued. Try selecting the job again.
The data set selected cannot be displayed. Either the data set is an internal reader data set, the data set name was invalid or the data set could not be found.
The job has been purged from the system and is no longer available.
A request failed to obtain information. The name of the request is <name>, <rc> is the return code from the service, and <rs> is the reason code.
The job name entered is not a valid job name. The only valid characters for a job name are #, $, @, the letters A-Z and the numbers 0-9. Also, the job name cannot start with a number. In some cases, mask characters are okay. If you receive this message when the only thing invalid are mask characters, then the job name must be entered without mask characters.
There were no eligible output data sets for the selected job. Output descriptors can only be displayed for output data sets that are closed.
The <cmd> command was issued without either a job name or job number. Issue the command again, specifying at least a jobname or number.
The active command was interrupted by either the user using the attention key or the loop prevention time out was about to occur. Enter another command to continue.
Output for job <jobname> is active on a device that is not attached to the current system. The delete line command cannot be used in this situation. Clear the field to continue.
The job is no longer active on device <devname>. Issue the REFRESH subcommand to update the display, or clear the line command to continue.
The <x> line command cannot be used for a job on the <xxxx> queue. Clear the line command to continue.
The line command <linecmd> is invalid for a nonexecuting job. Clear the line command to continue.
The line command <linecmd> is invalid for a nonexecuting job. Clear the line command to continue.
The action used on job <jobname> can only be used on jobs that are executing on the current system.
The cancel command cannot be used for job <jobname> because detail data is not displayed for this job. Enter OPTION DETAIL to display detail data and then reissue the cancel command.
The <command> command was processed successfully.
The value specified with the <function> function is invalid.
Check the <command> documentation for valid parameters and options.
An attempt to issue a command for the <cmd> command failed. Use the LISTLOG command to check for messages pertaining to the failed command.
The action used on job <xxxxxxxx> can't be performed because the job wasn't on the right JES queue. Check the documentation for information about the proper queue.
An attempt was made to release job <xxxxxxxx> but the job is not held.
An attempt was made to hold job <xxxxxxxx> but the job is already held.
An attempt was made to delete job <xxxxxxxx> but the job has protected output and the PROT option was not used. Enter the command again with the PROT option.
An attempt was made to restart job <xxxxxxxx> but the job is not a batch job.
The <cmd> command was not valid for a job running on JES3.
Informational only. Used for tracing.
|
Copyright © 2014 CA.
All rights reserved.
|
|