The command <comname> is an invalid command and is not a subcommand of the active command. Issue the RECALL command to redisplay the invalid command on the command line. Issue a valid command.
A command module has called the PC of this product, and the PC has terminated due to an abnormal condition. The <idn> variable is an identifier that can be JCSR, ROSR, or XMDS. <reg15, reg0>, and <reg1> are the values in Registers 15, 0, and 1, respectively. If <reg15> is greater than 001C, issue the STATUS command and print the contents of the entire display (PRINT ALL). Note the circumstances in which the error occurred. Contact CA Technical Support.
The attempt to load module <modname> has failed. If <modname> is a SYSVIEW module, check to make sure the SYSVIEW modules are in a linklist library. Also, check the console log for the reason the load failed.
The request for storage for a workarea failed. The session terminates. Increase the region size of the application where SYSVIEW is running. The routine name <rtn>, offset <offs>, and length of storage requested are also displayed in the message.
The display is at the beginning of the data or info rows or columns.
The display is at the end of the data or info rows or columns.
An error has occurred during processing of the input data typed by the user. <code> is the return code. If this message is received while running the batch interface, check to make sure the first input control card is a DATA control card that defines the user ID. If this message is received repeatedly, note the return code and the circumstances in which the error occurred. Contact CA Technical Support.
The scroll command parameter <scrollamt> contains an invalid number of lines or columns to scroll. Make sure the number is a decimal number. Also, make sure any input data left on the command line is cleared before a scrolling PF key is used.
The command has attempted to create another level, but that attempt exceeds the maximum number of nested levels. Return to the previous level before issuing the command to create another level.
The parameter <parmnumb> specified with the command did not specify the ending character delimiter. Issue the RECALL command to redisplay the command on the command line. Specify the ending character delimiter on the <parmnumb> in error, and issue the command again.
The parameter <parmnumb> specified with the command exceeds the maximum parameter length. Check the command documentation for the maximum parameter length. Issue the RECALL command to redisplay the command on the command line. Issue the command again with a valid length for the <parmnumb> in error.
More parameters are specified with the command than the command supports. Check the command documentation for the correct parameter format. Issue the RECALL command to redisplay the command on the command line. Issue the command again with the correct number of parameters.
The command has been entered without a parameter; the command requires at least one parameter. Check the command documentation for the correct parameter format. Issue the RECALL command to redisplay the command on the command line. Issue the command again with at least one parameter.
User <userid> has issued a command and the command has the message action set. The message shows the user ID <userid>, the command <command>, and the command parameters <comparms>. For details on setting the message action for a command, see the Security Guide.
The user <userid> has issued a command for a job with the message action set. The message shows the user ID <userid>, the command name <comname>, and the job <jobname>. For details on setting the message action for a job, see the Security Guide.
The MVS command has been used to issue the operator command. The message displays the user-issued command <operator_command>.
The PF key pressed is not defined in the profile for the active command. Issue the PROFILE or SET command to define a value for the PF key.
The SYSVIEW main common anchor block could not be located or created.
The command entered requires information from JES2, but JES2 is not active. Issue the command again when JES2 is active.
The command is disabled.
An attempt to logon failed because the correct password or passphrase was not entered and the retry limit was reached.
The highlighted input fields contain invalid data. Check the command documentation for correct values for the highlighted input fields.
The global load for the specified module failed with the specified abend code.
The attempt to dynamically allocate the JES2 spool volume <volname> has failed. <code> is the return code. For a definition of the return code, see the SVC 99 Return Codes section in the IBM documentation.
The DEVTYPE macro has failed for JES2 spool volume <volname>. Note the circumstances in which the error occurred. Contact CA Technical Support.
The attempt to open the JES2 spool data set has failed. The message shows the volume name <volname> of the spool volume that could not be opened. Note the circumstances in which the error occurred. Contact CA Technical Support.
When delete confirmation is in effect, the command is ready for confirmation. Enter YES on the command line to confirm all highlighted line commands. Clear the line command to cancel the request.
The command <comname> has an invalid parameter. Issue the command again, using a valid parameter.
An invalid release of the SYSVIEW module <modname> has been loaded. Make sure the correct SYSVIEW modules are in the linklist or STEPLIB library. If you are using a STEPLIB library, make sure all of the STEPLIB libraries are APF authorized.
The request for storage during initialization failed because there is not enough available storage. The session terminates. Increase the region size of the application where SYSVIEW is running.
The attempt to load a module named <modname> failed. The reason for the load failure is <reason>. Check to make sure the module <modname> is in an accessible library. Also, check the console log for any additional load failure messages.
The SYSVIEW address space requires a startup PARMLIB member name to be supplied. Make sure a member is specified by the MEM= parameter in the SYSVIEW procedure and that the member exists in the SYSVIEW PARMLIB data set.
An invalid member name or data set (member) has been specified.
A command module tried to obtain storage for a work area, but there was not enough storage available. Increase the region size.
User <userid> has specified an incorrect password when attempting to use SYSVIEW. The session terminates. Verify your password with your SYSVIEW Security Administrator.
The user <userid> has attempted to use a command with a jobname for which she or he is not authorized, and the message action is set for a jobname. The message shows the user <userid>, the command <command>, and the job <jobname>. For details on setting the message action for a job, see the Security Guide.
The user <userid> is not authorized to use SYSVIEW.
Output viewed with ISPF edit cannot be saved.
The command <cmdname> requires the feature <feat> that either was not requested or was not authorized. Features refer to options and components selected in the system configuration parmlib member parameters:
See the Installation Guide for more information.
The user <userid> has issued the command <command> for resource type <restype> with resource value <resvalue>. The message action is set for this resource. For details on setting the message action for a resource, see the Security Guide.
The user is not authorized to issue the MVS command <comname>. If you must use the command, contact your Security Administrator for permission.
The attempt to access the copy data set failed because the data set name specified in the profile is invalid. Check the GENERAL section of the profile for the copy data set name.
User <userid> has issued the MVS command <comname> with the message action set. For details on setting the message action for an MVS command, see the Security Guide.
The user <user> has issued a command for an output file that has the message action set. The message shows the user ID <userid>, the command type <cmd>, the jobname <jobname>, the job number <num>, and the ddname <ddname> of the output file. For details on setting the message action for an output file, see the Security Guide.
This message is logged when an "STIMERM CANCEL" was issued to cancel a timer interval and it was found that the timer interval was not queued meaning that the timer exit had run or will run. This message identifies the TCB address, the timer identifier, the ECB address, and the ECB contents for which a WAIT will be issued.
The attempt to establish a timer has failed for the LOG or JOBS task. The task terminates. <code> is the return code.
The attempt of the LOG task to get storage has failed. The LOG task terminates. It is possible that there is not enough storage available in the SYSVIEW address space. <code> is the return code. Try increasing the region size for the SYSVIEW address space. If you require assistance, note the return code and contact CA Technical Support.
This message is logged following the message:
GSVX553W Truncation occurred during variable substitution
to display the source string that was being processed when the variable scan-and-replace encountered a truncation problem.
The cancel line command has been entered for a job on the Activity Display after the job has executed. Clear the line command, or enter the REFRESH subcommand to continue. Informational only.
In order to get information for some of the displays, RMF monitor III must be active. Start RMF monitor III and try the command again.
A request for data from RMF timed out. Retry the command again. If this message is received repeatedly, contact CA Technical Support.
Either the MODIFY command or the initialization parameter <comname> entered for the SYSVIEW address space is invalid. For valid MODIFY commands and valid initialization parameters, see the Administrator Guide.
An invalid keyword has been entered. Review the command syntax.
A keyword was entered that requires a value. A value that was supplied is not valid.
The log stream specified does not contain the correct type of data or has not been defined in the LGLOOKUP parmlib member.
Data set dynamic allocation has failed because of an invalid <parmname> parameter value.
This message indicates that a function has been initialized, terminated, or the action specified.
The release validation process failed for the module named <modname>. The release and build that were found and the release and build required are displayed if available. When this message occurs very early in the initialization process the format will be:
Invalid release for module <modname>
The ddname <ddn> was found to be allocated and this caused the call to "XINSR INSTALL" to be bypassed.
The NSS-PC module named <modname> is not at build <bld> or higher. This can occur when multiple releases of CA SYSVIEW are in use on the same system and the NSS-PC modules are at the older release. The modules of the new release have not been installed because the SYSVIEW server address space has not yet been started to install the newer modules
The panel <panname> contains no displayable lines. The panel library is specified in the system configuration parmlib member parameter:
Dsn-System-PANELLIB <paneldsn>
Make sure <panname> is not corrupted.
The secondary keyword <seckwd> is invalid for the <type> and primary keyword <cmd prikwd>. An example of this message is <BIG keyword invalid for SET SCREENSIZE command>.
The <var1> variable will be either command or module. The <var2> variable is the name of the command or module which was not found in the command table. If you receive this message, note the circumstances in which it occurred and contact CA Technical Support.
The MVS device lookup service has failed, with return code <code>. For more information, see the appropriate IBM documentation. Contact CA Technical Support.
The <name> <type> was issued with more than 1 parameter.
The <name> <type> was issued with more parameters than are allowed.
The issued <type> requires a closing delimiter on the parameter <parm>. Issue the <type> again, specifying a closing delimiter.
The parameter <parm> is too long. <xxx> is the maximum length of the parameter. Issue the <type> again, specifying a parameter of valid length.
The <name> <type> has been issued with parameters. The <type> does not have any parameters. Issue the <type> again, without specifying any parameters.
The keyword <kwd> specified with the <cmd> <type> is not valid for the <type>. Issue the <type> again, specifying a valid keyword.
The ASID <asid> is inactive.
The ASID <asid> specified by job <jobname> is inactive.
The job <job1name> has ended and job <job2name> is now running.
The SYSVIEW NSS-PC cannot gather information from the desired address space in the allotted time. This situation usually indicates a major MVS problem with the address space. The target address space, therefore, is internally switched back to the HOME ASID to avoid any more interaction with the address space. You can retry the command, but we recommend that first you use the ACTIVITY and CONSOLE commands to check the overall status of the system.
The NSS-PC has failed because the address space <asid> is not active.
The issued command requires information from another address space. The resulting NSS-PC to gather that information has failed because the target address space did not respond within 15 seconds. This situation usually occurs when the target address space is swapped out and the MVS SRM (system resource manager) cannot or will not swap it back in.
An error has occurred during scanning for the data <data> in the VSM control blocks. Contact CA Technical Support.
The scroll amount field (Scroll ===>) has been modified with an invalid value. Specify a valid scroll amount. Valid values are the same as the parameters of the scroll commands.
The ddname <ddname> was found to be allocated and this forced a <condname> condition. This is just for testing.
The current ASID was initially selected by ASID, and the active jobname was an initiator. Since then, the job <jobname> has started executing in the initiator.
The batch job <jobname> that had been active in the selected address space has ended. The initiator is now inactive.
There was not enough storage available to display all of the information for the command. <nnn> is the number of lines not displayed.
An error has occurred during MVS control block processing, and some information is unavailable.
The <cmd> command failed while processing MVS control blocks. The <errinfo> field contains additional information about the error. Contact CA Technical Support.
Dynamic allocation of the data set <dsname> has failed. The IBM error codes <xxxxxxxx> are supplied. For an explanation of the error codes, see the IBM documentation in MVS Authorized Assembler Services Guide.
Dynamic allocation of the data set <dsname> has failed because the data set is not cataloged. Catalog the data set.
Dynamic allocation of the data set <dsname> has failed because the data set cannot be found on the volume specified in the catalog.
Dynamic allocation of the data set <dsname> has failed because the data set resides on a volume that is not mounted.
Dynamic allocation of the data set <dsname> has failed because some other job has exclusive control of the data set.
Dynamic allocation of the data set <dsname> has failed because it is not a valid data set name. Try the allocation again, using a valid data set name.
The <comname> command requires the <parmname> parameter. Issue the command again, specifying the required parameter.
No match is found for the parameters specified either with the command or on the parameter line.
The keyword <keyname> is not long enough to be unique. The command supports more than one keyword parameter. Issue the command again, using a unique keyword. For example, for the valid keywords TAPE and TP, T would be ambiguous but TA would not.
The ddname <ddname> was found to be allocated and this forced an "SGAT block not found" condition. This is just for testing.
An SVC 99 request has failed for <servname>, which can be one of the following:
<codes> is the error codes. For an explanation of the error codes, see the IBM documentation in MVS Authorized Assembler Services Guide.
The session of a user has timed out. For details on setting timeout values for secrutiy groups, see the Security Guide.
The <cmdname> command is invalid because the SYSVIEW XXMDS nonspace switch PC services are not available.
Logon processing has terminated because a PF key was pressed while the user ID and password prompt screen was displayed.
The attempt to start the SYSVIEW address space with the PRIMARY keyword in the initialization parameters has failed because a primary SYSVIEW address space is already active. If another SYSVIEW address space must be started, remove the PRIMARY keyword from the initialization parameters.
An attempt to display the JCL for a job failed because all of the necessary files were not available. A job must be submitted on the current system in order to display the JCL for the job. Also the job must not be a transaction job.
Informational only.
Informational only.
The terminal you are using to sign on to SYSVIEW is not supported by SYSVIEW. SYSVIEW supports 3270-type terminals only. Use another terminal to sign on to SYSVIEW.
The attempt to start the interface <interface> has failed because the interface is already active.
The attempt to set up a recovery routine has failed. Try starting the session again. If the message is received repeatedly, contact CA Technical Support.
The attempt has been made to change the current logging options options for a CICS logger task. The current state or configured options will not allow the new request.
The initialization parameter <xxxxxxxxxxxxxxxxxxx> is invalid for the SYSVIEW application. Verify that the initialization parameters of the application are correct.
Informational only.
Interface <name> has initialized and is ready to be used.
The Status Display has been requested, but there are no active users to display.
A status or trace display has ended.
The maximum number of users allowed for interface <xxxx> has been reached. A new user has tried to use the interface and the request is denied. Increase the MAXUSERS initialization parameter for the interface.
Informational only.
User <user> tried to sign on to SYSVIEW through an interface, but could not be accepted. <code> is the return code. Note the return code. Contact CA Technical Support.
The input data cannot be received. <code> is the return code. Note the return code. Contact CA Technical Support.
The necessary resources to establish a new user for the interface are not available. <code> is the return code. If this message is received repeatedly, note the return code. Contact CA Technical Support.
This error occurs when a screen cannot be sent to the user. <code> is the return code. If you receive this message repeatedly, note the return code. Contact CA Technical Support.
User <userid> is the target of either of the following:
<code> is the return code. Note the return code. Contact CA Technical Support.
Interface <name> is performing shutdown processing. No logons are allowed.
The attempt to copy output to the copy data set has failed because a print file is opened to the copy data set. Issue the PRINT CLOSE or SNAP CLOSE command, and try to copy again.
There is not enough storage to hold the data for a status or trace display. Try increasing the region size of the application where SYSVIEW is running.
The attempt to cancel user <userid> has been accepted.
The attempted cancel of user ID <userid> is invalid because the user ID is either not specified or not active. Issue the command again using a valid user ID.
User <userid> has requested to shut down interface <interface>.
User <userid> has requested that interface <interface> be shut down, but users are still on the interface. The interface will shut down as soon as the active users have terminated their sessions. If you want to force an immediate shutdown, enter the STOP command. Informational only.
The LOG task has found that there are no SYSLOG output data sets on the JES2 spool.
The parameter <parm> is invalid for the TRACE command.
An attempt was made to start a trace, but the trace is already active. If you want to start a different trace, stop the current trace before starting another one.
The request to turn off a trace has failed because the trace is not active.
A trace has been activated.
A trace has been stopped.
The request to list the trace data has found no data to display.
A valid module identification area could not be found in the <modname> module. The module release and build validation process failed. When this message occurs very early in the initialization process the format will be:
Invalid ident for module <modname>
An abend has occurred in the SYSVIEW interface <xxxx>. A dump has been taken. Obtain the dump output. Contact CA Technical Support. Restart the interface.
The command <comname> either does not apply to or is not available from the application where it is specified.
Informational only.
An attempt was made to exit a display before correcting the errors. Correct the highlighted lines or use the CANCEL command to cancel the changes.
An attempt was made to acquire CSA or SQA storage, but there was not enough contiguous storage available to satisfy the request. Use the COMMON command to determine if common area storage is fragmented or exhausted. The <idn> variable is a NSS-PC identifier that can be JCSR, ROSR, or XMDS.
Informational only.
Command <cmdname> could not be invoked because no valid request was found in member <member>.
The update time interval <xxxxxxxx> has been changed to <num> seconds for the JOBS or LOG task in the SYSVIEW address space.
The job with the name and number of <jobname jobnum> specified cannot be found.
All of the output files for the selected job have been requeued or deleted. If this message is received on the Listjobs Display, issue the REFRESH subcommand and try the L line command again. If this message is received on the Listfile Display, issue another command to continue.
There are multiple jobs in the system with the name <jobname>. The job with the <pos> job number has been selected. <pos> can be Highest, Lowest, Newest, Oldest, or Executing. For details, see the MULTJobs variable of the SET command.
There are no authorized data sets for the selected job.
There were jobs that matched the parameters entered, but none were authorized. This message is informational.
Informational only.
Not enough storage was available to display all of the data. If possible, specify parameters that reduce the amount of data to display.
The line command specified is invalid. Try again with a valid line command. For a list of valid line commands, see the online help system.
The line command specified is not valid on the line from which it was issued. To see the information and restrictions about line commands, use the online help system.
A WHERE subcommand was issued to search for a specific or generic member name and no match was found in any of the allocated libraries.
The response to the VM command is longer than can fit in a single 4 KB buffer (a VM restriction). The number of bytes of responses <nnnnn> is discarded.
The highlighted field in the body of the display is invalid. It contains embedded blanks where none are allowed. Remove the embedded blanks and issue the command again.
The highlighted field in the body of the display is invalid. It contains nonnumeric data where numeric data is required. Remove the nonnumeric data and issue the command again.
The line command <linecmd> is not a valid line command from the current screen display. Try again with a valid line command. For a list of valid line commands, see the online help system.
Line command <linecmd> is not long enough to be unique. Enter enough characters to uniquely identify the line command.
The subcommand <subcommand> is invalid from the current active command display. Try again with a valid subcommand. For a list of valid subcommands, see the online help system.
Subcommand <subcommand> is not long enough to be unique. Enter enough characters to uniquely identify the subcommand.
The issued subcommand or line command requires confirmation, and the setting of the DELETE CONFIRMATION option is YES. Enter YES to continue execution of the indicated function. Enter ALL to continue execution of all the indicated functions. Enter anything else to abort execution of the indicated function.
This message appears if the response to message GSVX160A was not YES.
YES was entered when no confirmation was pending. Issue the command that requires confirmation again and then enter YES.
A WHERE subcommand was issued to search for a member but there are no libraries available to search.
The version of JES2 installed <ver1> is no longer supported. The minimum level of JES2 supported is <ver2>. Informational only.
Informational only.
The command <cmd> is not valid in the installed level <lvl-found> of the software component <name>. The required level of the software component is <lvl-req>. Possible values for <name> are MVS, DFP, TSO/E, ISPF, QUICKREF, and VTAM.
The LOCATE command was issued without a label name or line number parameter. Issue the LOCATE command again specifying either a label name or a line number.
The label <label-name> supplied with the LOCATE command was not found in the table of labels defined for the current command. Issue the command again using a valid label. Execute the LABEL command without a parameter to display the current contents of the label table.
The label <label-name> was found for the current command <command-name> and the line was located. This message confirms that the requested action occurred.
The line number <line-number> defined for the label <label-name> is greater than the currently defined number of data lines. Issue the command again using a valid label. Execute the LABEL command without a parameter to display the current contents of the label table.
The service routine <service-routine-name> failed with abend code <code>. Contact CA Technical Support.
Command <cmdname> requires the services of ISPF. Access ISPF and issue the command again.
Command <cmdname> cannot be executed from the <intfc> interface. Check the online help system for a list of valid interfaces.
Command <cmdname> cannot be executed because the load for required module <modname> failed. Determine why the load failed and issue the command again.
The <appldesc> application requested special <text> execution attributes. The values for <text> can be the following.
Command <cmdname> abended with the code <code>. Determine why the abend occurred and issue the command again.
A subsystem call failed with a return code of <code>. The first two bytes are the subsystem function. The last three bytes are the return code from register 15. Note the return code. Contact CA Technical Support.
The action to be taken for a job cannot be processed. <code> is the return code. Note the return code and the circumstances in which the error occurred. Contact CA Technical Support.
The program name <pgmname> must be APF authorized. This usually indicates an error in the product installation. Review the installation process and retry the failing job if any mistake was found and corrected. Contact CA Technical Support.
This general purpose error message indicates that the command <cmd> was issued with the keyword <kwd> but the required value for the keyword was not supplied. For information on the command in question, see the online help system.
Informational only.
An ASID selected with the ASID command had become inactive and is now active again because an initiator has started.
An ASID selected with the ASID command had become inactive and is now active again because an initiator has started and is processing a batch job.
A change was detected in jobnames in an ASID selected by the ASID command.
A job executing in ASID <asid> is in transition--starting, ending, or abending.
AR mode is on for a data space that is no longer active. Use the AR command to set AR mode to OFF, the DSID command to switch to another data space, or the ASID command to switch to another address space.
Service <srvcname> failed with the indicated return codes. Contact CA Technical Support.
There was not enough storage to return all data for service <srvcname>. Contact CA Technical Support.
A link to the <cmdname> command was issued. This is not allowed.
This is a general purpose error message indicating that an invalid keyword was supplied. Review the documentation for the <cmd> <type> and the options allowed for the <kwd> keyword.
This is a general purpose error message indicating that a required keyword was omitted. Review the documentation for the <cmd> <type> and the options allowed for the <kwd> keyword.
Service <srvcname> failed with the indicated return codes. Contact CA Technical Support.
This is a general purpose error message indicating that a value is required for the <kwdname> keyword. For information on the command that was entered, see the online help system.
This is a general purpose error message indicating that an invalid value was specified for the <kwdname> keyword. For information on the command that was entered, see the online help system.
This is a general purpose error message indicating that a parameter started with the character-delimiter character but no closing character-delimiter character was found.
An unsupported character-string qualifier was used on the <parmname> parameter.
The END or RETURN command was issued to terminate the session and the CONFIRMTERM option was set to YES. In response to the message prompts, reenter the END or RETURN command to confirm your intention to terminate your session, or enter anything else to cancel the termination command.
User <userid> attempted to issue the MVS command <mvscmd> but was denied by a security rule. That rule had the message action set. For details on setting the message action for an MVS command, see the Security Guide.
The request has been successfully completed.
The specified attribute has been set for the command.
An attempt was made to set an attribute for a command. An invalid command name was specified.
An attempt was made to set an attribute for a command. The specified attribute is invalid.
The resolved length of the capture data set name high-level qualifier is longer than the maximum length allowed of 28. The capture data set name high-level qualifier will be used but the time and date qualifier (.Thhmmss.Dyymmdd) added to the end of the name will be truncated.
This message displays the capture data set name high-level qualifier.
Nucleus load processing failed to complete. The SYSVIEW session terminates. This message should be preceded by one or more messages that describe the reason for the failure.
Nucleus initialization processing failed to complete. The SYSVIEW session terminates. This message should be preceded by one or more messages that describe the reason for the failure.
The SYSVIEW transaction tranid has completed normally under CICS.
The task that handles the user's data has terminated in the SYSVIEW address space. This could be due to user inactivity and a timeout occurred or the subtask abended. If a timeout did not occur, note the circumstances. Contact CA Technical Support.
The attempt to attach the SYSVIEW subtask under CICS has failed. <code> is the return code. Try entering the SYSVIEW transaction again. If this message is received repeatedly, note the return code. Contact CA Technical Support.
The control block used for communicating with its CICS subtask cannot be found. Try entering the SYSVIEW transaction again. If you repeatedly receive this message, Contact CA Technical Support.
The subtask under CICS has terminated, possibly because the timeout value has expired for the session. Try entering the SYSVIEW transaction again to start another session. If this message is received repeatedly, Contact CA Technical Support.
The CICS interface must be started in SYSVIEW address space before using the SYSVIEW transaction. For information on how to start the CICS interface, see the Administrator Guide.
The CICS interface is in the process of shutting down. The SYSVIEW transaction cannot be used until it is restarted. For information on how to start the CICS interface, see the Administrator Guide.
An attempt was made to communicate with the SYSVIEW address space, but the attempt failed. If this message is received repeatedly, note the return code. Contact CA Technical Support.
An attempt was made to load a SYSVIEW module, but the load failed. Check the SYSLOG for the reason why the load failed.
An attempt was made to call a SYSVIEW module but the call failed. If this message is received repeatedly, note the return code. Contact CA Technical Support.
An attempt was made to communicate with the SYSVIEW address space, but the attempt failed. If this message is received repeatedly, note the return code. Contact CA Technical Support.
A request to the Dynamic Exit Services failed.
For more information, see the MVS Authorized Assembler Services Reference.
A request for storage has failed.
A attempt was made to load a module for use with dynamic exits. The load failed.
module - Name of module being loaded
A attempt was made to initialize a dynamic exit load module. The initialization call has failed.
A request was made to access SMF collected data. Data collection is not active.
A request was made for specific data from a collection log. The requested data is no longer available on that log.
A request was made to format an SMF record. The module used to format the record was not found. The module names are specified by SMF record type in the parmlib member SMFTYPE.
module - Module name
A request was made to format an SMF record. The module used to format the record abended.
module - Module name
An internal trace message used to debug hashed data structures.
The task has successfully connected to the specified log stream.
An attempt to write to the specified ddname failed.
A request was made to connect to the specified subsystem ID. The ID was not found.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Metrics data is being sent to the Time Series Facility server for the listed owner and hierarchy. The number entities is a count of unique entity instances at the lowest level.
Messages GSVX291 and 292 are displayed with debugging information.
Messages GSVX291 and 292 are displayed with debugging information.
The TSF task, logger process has completed and the indicated number of buffers were processed, sent and discarded.
TSF data is being sent to the TSF logger.
TSF period data collection is being resynchronized.
The ISPF interface has requested ISPF services <serv>, but the request has failed. <code> is the return code. Make sure you are using ISPF Version 2 or higher. If you are, note the return code. Contact CA Technical Support.
An error message was returned by ISPF after a request was made for ISPF services. The message text, <message-text>, is the actual message returned by ISPF.
The panel <panname> cannot be found. Note the circumstances in which the error occurred. Contact CA Technical Support.
The panel <panname> cannot be displayed because it is not at the correct SYSVIEW release <rel>. Verify that the SYSVIEW ISPF interface is correctly installed. Contact CA Technical Support.
The command table <tabname> is either not in the correct format or not at the proper level. Verify that the ISPF interface is correctly installed. Contact CA Technical Support.
The command table <tabname> cannot be displayed because it is not at the correct SYSVIEW release <rel>. If you are using a supported release, note the circumstances in which the error occurred. Contact CA Technical Support.
Update mode is in effect. To end update mode, do one of the following:
Update mode is in effect. To end update mode, press the RESET key and then the PA1 key.
Update mode is in effect. To end update mode, press the ATTN key.
The return code from the ISPF EDIT facility indicated that data was saved and either the data set was not a PDS or no member name was specified on the EDIT command.
The return code from the ISPF EDIT facility indicated that data was saved and a specific member name was used with the EDIT command. <memname> is the name of the member that is saved.
Informational only.
An entry in parmlib member <member> is invalid.
A status of an MVS defined threshold limit has changed.
A request was made to add a table entry. The entry name was invalid.
A request was made to add a table entry. The entry name already exists.
The request for data failed. Return code <rc>.
The field <field> requires input to process the requested function.
A status of a defined threshold limit has changed for the following components: WebSphere MQ, IMS, TCP/IP
The argument cannot be specified as a generic or wildcard argument. A threshold was defined with an argument value of "*" or "=". A non-generic argument must be specified.
The <value> specified is not a valid value to the parameter <parm>.
An invalid parameter was specified while defining or changing a threshold entry.
A request was made to create a monitoring entry or definition for the variable specified. This variable is obsolete.
<variable> - Obsolete variable name
Internal debugging message. Contact CA Technical Support for more information if this message is displayed.
A request for WebSphere MQ information has failed.
A request to UNIX System Services has failed.
Common errors:
For more information, see the UNIX System Services Error Message Manual.
A trace message logging the start and end time of a data collection interval.
Dataspace corruption has been detected.
Informational only.
A trace message logging the start and end time of a timed event
A request was made to add a threshold, monitoring, or state definition. The requesting commands data collector does not own the requested variable.
Example: The MQTHRESH command tried to add an MVS threshold.
A request was made to a threshold, monitoring, or state definition. There is a type mismatch.
Example: The request was made to a threshold variable. Problem was that the variable requested was a state variable an not a threshold variable.
A data collection diagnostics message.
The command entered is trying to connect to the data collection data store.
Possible problems:
Internal debugging message displaying the current value for a data collection variable. Contact CA Technical Support for more information if this message is displayed.
The UNIX System Service has not been successfully initialized. USS is required for the Unicenter agents.
CAICCI is not active. CAICCI is part of CA Common Services.
A request to CA Common Services for z/OS has failed. Return code information is provided.
A request to CA Common Services for z/OS has failed.
This message displays the origin or destination communication server identifier.
This message displays the origin or destination communication client identifier.
The <ddn> ddname can not be allocated to a SYSIN data set.
The batch interface has detected invalid DCB parameters for the <ddname> ddname. For a description of the valid DCB parameters for the SYSPRINT and SYSIN data sets, see the Administrator Guide.
The batch interface has tried unsuccessfully to the <ddname> ddname. Try running the job again. Contact CA Technical Support.
The SCROLL request was ignored because the previous command generated an error message. Correct the command that caused the error and try running the job again.
The batch interface module has encountered the invalid keyword <keyword-statement> while processing the input control cards. The statement is ignored, and processing continues with the next keyword statement. Check the keyword statement and run the job again.
The batch interface module has encountered the invalid keyword parameter <keyword-statement> while processing the input control cards. The statement is ignored, and processing continues with the next keyword statement. Check the keyword statement and run the job again.
The batch interface module has encountered an unbalanced set of parentheses in processing input control cards. The message shows the entire keyword statement <keyword-statement>. The statement is ignored, and processing continues with the next keyword statement. Correct the keyword statement and run the job again.
The batch interface module finds the subscript on the DATA keyword to be invalid. The message shows the entire keyword statement <keyword-statement>. The statement is ignored, and processing continues with the next keyword statement. Correct the DATA keyword, specifying a valid subscript. Run the job again.
The batch interface module finds that the subscript on the DATA keyword does not correspond to an input field on the current display. The message shows the entire keyword statement <keyword-statement>. The statement is ignored, and processing continues with the next keyword statement. Correct the DATA keyword, specifying a keyword that corresponds to an input field on the current display. Run the job again.
The batch interface module finds that the input data for an input field is longer than the input field. The message shows the entire keyword statement <keyword-statement>. The statement is ignored, and processing continues with the next keyword statement. Correct the length of the input data and run the job again.
The EXECBAT module has encountered keyword <xxxxxxx>, which is either not expected or not allowed. If <xxxxxxx> is COMMAND, specify a user ID and password with DATA keywords at the beginning of the input control cards. If <xxxxxxx> is SCROLL, check that the DUMP command is not active. You cannot use the SCROLL command when the DUMP command is active.
This message is displayed when using the API interface. Not all of the data was returned because the line limit maximum was reached. If more data is required, increase the line limit maximum by using the LIMIT keyword.
This message is displayed when using the API interface. The keyword <keyword> is not a valid field name or input field number. Change the keyword value to a valid input field name or number.
The batch interface module has encountered the invalid statement while processing the input control cards. The statement is ignored, and processing continues with the next statement. Check the statement and run the job again.
This message is displayed when the batch interface module is invoked in a TSO foreground address space. It requests the user to enter the next batch request to process or the string "/*" to exit the batch interface.
This message is displayed when the batch interface module is invoked in a TSO foreground address space and the user has entered the SCROLL statement. It requests the user to hit the ENTER key to continue scrolling or to hit any Fnn key to stop scrolling.
Abend <abncd> occurred attempting to open the ddname <ddname>.
Batch initialization failed with abend <abncd>.
The batch interface was terminated because the user hit the ATTN key. This can only happen if the batch interface was executing in a TSO foreground address space with the SYSIN and SYSPRINT ddnames allocated to the terminal.
A request has been made to a specific CICS logger named <taskident>.
action values:
A request for a linkage index with value <lx> has been made.
The specified request <request> has failed. The return code from the request is indicated by value <rc>.
The specified request <request> has failed. The request was directed at the dataspace with stoken <stoken>. The resulting values for registers 15 and 0 are shown in <r15> and <r0>.
A request was made to dynamically increase the extended private storage size for the address space.
<original> indicated the size prior to increasing its value to <new>.
A request for a authorization index with value <ax> has been made.
The CICS logger task has detected a CICS data collection address space as inactive. A recovery process is performed to resync the collection blocks.
The current status of ASN-LX reuse and address space reuse is displayed.
If all of the above values are not YES, then the address space will not be reuseable.
The select entry does not have a defined threshold or state rule.
The a specific monitoring definition is not required for the selected entry.
Internal debugging message displaying the current value for a data collection process. Contact CA Technical Support for more information if this message is displayed.
A request to export data has been made. The data has been written to the data set and member specified.
A request to checkpoint data has been made.
An event notification request has been made to CA OPS/MVS that has failed. The return code and reason code is given.
Return code and description:
No CA OPS/MVS subsystem is active to process an event notification request.
An event notification request has been made to CA OPS/MVS that has failed. No more attempts will be made. The interface has been disabled.
Internal log message.
Internal log message.
A request to export data has been made. The request has failed. Check reason for additional information.
A request to checkpoint data has been made. The request has failed. Check reason for additional information.
A task has been started. The task is being started using a "Warm" or a "Cold" method.
The user has invoked cursor selection within the information or overview section of the display.
The SHOWCB macro, used to determine the length of the RPL, has failed. <code> is the return code. Note the return code. Contact CA Technical Support.
The open has failed for the VTAM ACB. The first half of the return code <code> is the contents of register 15 in hexadecimal. The second half of the return code is the hexadecimal error field from the ACB. If the return code is 0008005A, make sure the APPLID is defined to VTAM and is active. Check the VTAM programming manual for the return codes from OPEN for an ACB. For more information, note the return code. Contact CA Technical Support.
The SETLOGON macro has failed in the GSVXVTAM module. <code> is the return code. Note the return code. Contact CA Technical Support.
An RPL error has occurred for a VTAM interface session. The user may have dropped their session without ending it properly. The return code <code> reflects fields from the RPL when the error occurred. The terminal ID <termid> and user ID <userid> are displayed in the message if they are available. If this message occurs repeatedly, note the return code. Contact CA Technical Support.
Informational only.
Informational only.
Informational only.
The SYSVIEW VTAM has completed initialization and is now ready to accept logons using the <applid>.
The SYSVIEW VTAM has completed initialization and is now ready to accept logons using the <applid> or <netnm> names.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
User session has been attached.
User session has been detached.
User session has been closed.
User session has been timed out by security. The LUname and userid that was timed out is displayed.
Informational only.
The text displayed is the output of one of the following console commands.
The system log data set (logical name) is not defined to this system. The command requesting this log data set is not available on this system.
The system log data set (logical name) is not active on this system. The command requesting this log data set displays the available data.
The log stream <logstream> is empty.
An invalid value has been specified. The acceptable minimum and maximum values are provided.
An invalid value has been specified. The acceptable minimum and maximum values are provided.
A request to print topics has completed.
An invalid parameter value has been specified.
A request was made to set a value. More than one function was requested. The entire request has been aborted.
An error has occurred while processing a parmlib member that contains configuration options.
A default value is being set for the configuration keyword.
The specified action has been taken against the data collection variable.
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.
All of these messages are part of the diagnostic data SYSVIEW issues when it abends. If any of these messages are issued, note the circumstances in which the error occurred. Contact CA Technical Support.
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.
User <userid> attempted to use the command <command> for resource type <restype> with a resource value of <resvalue> but was denied. The message action is set for this resource. For details on setting the message action for a resource, see the Security Guide.
User <userid> attempted to use the resource type <restype> with a resource value of <resvalue> but was denied. The message action is set for this resource. See the Security Guide for details on setting the message action for a resource.
User <userid> used resource type <restype> with a resource value of <resvalue>. The message action is set for this resource. For details on setting the message action for a resource, see the Security Guide.
Informational only.
Informational only.
This message is displayed when there is no authorized data to display. The security rules determined that no data should be displayed.
A maximum of 8 discontiguous variable length masking character is allowed. This limit was exceeded.
An internal error occurred during processing. Note the circumstances in which the error occurred. Contact CA Technical Support.
The requested function is only available when executed using a CLIST or through the REXX exec API.
An attempt to dynamically add or delete OUTPUT JCL statement values failed. funcname is OUTADD or OUTDEL. Note the circumstances in which the error occurred. Contact CA Technical Support.
An input data stream longer than 256 characters was received from a cleared screen. The input is rejected.
This is a generalized message used to indicate that some requested function has been successfully completed.
An attempt to display an output file failed because the output file could not be found. The output file could have been deleted.
The specified data is not a valid subcommand.
The specified data is not a valid data set name.
The current command input string ended with the command continuation character. Any data entered has been added to the pending command string. Continue to enter the rest of the command or use any PF key to discard the entire command.
A PF key was entered in response to message GSVX515I. The pending command input has been cleared.
The total maximum command length of 256 characters has been exceeded.
An explicit cursor data character was encountered in the command input string but the cursor was not positioned within the data rows.
An explicit cursor data character was encountered in the command input string but the cursor location data could not be determined.
An explicit cursor data character was encountered in the command input string but nothing was found at the cursor location.
The indicated command has been terminated prematurely by hitting the ATTN (or PA1) key.
Informational only.
Invalid data was entered in the indicated field.
A value must be entered in the indicated field.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
A request to the specified function has failed. The return code should be used to determine the reason for failure. Additional messages may be present.
Informational only.
Informational only.
During user logon, the first or second (pswdpos) password entered was too long. Passwords must be no more than eight characters long.
During user logon, the password or passphrase entered was not correct. Enter the correct password or passphrase to continue. If you are using a passphrase, ensure your logon id has the passphrase attribute.
The password or passphrase entered during user logon has expired. Enter a new password twice separated by a slash. The second password is required to verify the first one. For a passphrase, enter it twice in the designated fields on the User Identification logon screen.
The security system rejected the new password or new passphrase. For passwords, reenter the new password twice separated by a slash. For passphrases, enter it twice in the designated fields on the User Identification logon screen. Passphrases can be 14-100 characters in length. If you are specifying a passphrase length between 9 and 13 bytes, the ICHPWX11 exit must be present.
The user ID used when logging on has been revoked by the external security system. Contact your security administrator to reinstate the user ID.
An attempt to validate a user through the SAF interface failed. SAF and RACROUTE return codes are supplied in the message along with the RACROUTE reason code. Check the external security product manuals for the reason the request failed. For RACF, the External Security Interface (RACROUTE) Macro Reference manual has an explanation of the return and reason codes.
An attempt to obtain a job ID from JES failed. Note the return and reason codes in the message. Contact CA Technical Support.
A command was entered that requires JES services, but they are not available now. Try again later when the JES subsystem is active.
The user ID used when logging on has not been defined to the external security system. Contact your security administrator to get the user ID defined.
Informational only.
Informational only.
Informational only.
The scroll command <scrlcmd> is not supported on the <cmd> command display.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
An attempt was made to acquire CSA or SQA storage, but there was not enough contiguous storage available to satisfy the request. Use the COMMON command to determine if common area storage is fragmented or exhausted. The <idn> variable is a NSS-PC identifier which can be JCSR, ROSR, or XMDS. <len>, <spn>, and <loc> are the length, subpool number and location of the storage requested.
Informational only.
Informational only.
This message is displayed by the SYSVIEW JOBS task when using the CCODE or NOCCODE parameter. It displays the status of completion code information checking.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
The requested member name could not be found in the specified data set.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
During product shutdown, the specified <task> did not terminate in the allowable amount of time. The task is forced to terminate.
Informational only.
Informational only.
An anchor block has been located at the specified address.
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.
Ensure that CA Common Services has completed initialization before starting the product. Only MVS related features will be available.
Informational only.
Informational only.
Informational only.
Informational only.
Indicates the current status of the LMP validation process.
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.
The CPU time that the <taskid> task consumed processing a request exceeded the request processing CPU time threshold.
The elapsed time that the <taskid> task spent processing a request exceeded the request processing elapsed time threshold.
Event management is starting or stopping for the specified queue manager. Event messages are passed to Unicenter.
Event management has terminated. The completion code for the task is provided.
Information involves the current status of monitoring for a specific queue manager.
A request was made to define monitoring for the specified variable. The variable specified is not variable that monitors a group resource.
An attempt was made to start a data collector. The feature required for the data collection was not requested in the system configuration parmlib member.
Threshold and exception initialization has been completed for the specified component.
The SMF data collection process will only collect records created by SYSVIEW.
A request was made to set a value. No parameter value was provided.
The requested function has been processed.
A request was made to set a value. More than one function was requested. The entire request has been aborted.
A request was made to set a value, but a specific function was not requested.
The value specified is not valid for the function.
The function specified is not valid for the object.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
An attempt was made to expand or collapse an entry that is not a group or does not contain any lower level entries.
Informational only.
Informational only.
Informational only.
This general purpose informational message lists the options in effect for the command <cmdname>. This message is typically generated in response to an OPTIONS subcommand.
Informational only.
The message echoes the command that has been issued.
If the keyword )ECHO has been processed within a source member, the data lines processed are echoed to the log. This message marks the beginning and ending of the echo process.
<p1> will contain Being or End.
This message is produced when echo processing is active for a specific source member.
A syntax error was found while reading the parmlib member <member>. The statement containing the error is displayed in <text>.
Informational only.
Informational only.
An internal statistical message used to evaluate the resources used by an event.
A request to obtain storage from a dataspace has failed.
A request to free storage from a dataspace has failed.
A new dataspace has been created.
A new ALET has been added to the dispatchable unit access list for the TCB.
An action has been taken on a data collection control area.
Internal debugging message. Contact CA Technical Support for more information if this message is displayed.
An external line command is being processed.
The external line command processor will replace the <field> with the specified <data> value.
The external line command processor found a substitution field that is invalid.
The external line command processor attempted to execute an invalid command.
The line command entered is not valid for the command and screen. The line command is valid for a different screen type associated with the command.
An external line command (XLC) definition has specified that a REXX exec will generated the command string to be used. The REXX exec name was not specified.
An external line command (XLC) definition has specified that a REXX exec will generated the command string to be used. The REXX exec name is not a valid exec name.
An external line command (XLC) definition has specified that a REXX exec will generate the command string to be used. The message displays the resulting command string.
An external line command (XLC) definition has specified that a REXX exec will generate the command string to be used. The REXX exec failed.
An external line command (XLC) definition has specified that a REXX exec will generate the command string to be used. The REXX exec did not return a command string.
The #PCSERV DEFINE macro issued to define the NSS-PC failed with return code <retcd> and reason code <rsncd>. Note the circumstances in which the error occurred and contact CA Technical Support.
A #PCSERV DEFINE macro was issued to either define or or redefine the NSS-PC (NonSpaceSwitch-PC).
This message displays information about the SYSVIEW NSS-PC (NonSpaceSwitch-PC). It shows the token, the epaddr of the NPCI module and the epaddr of the NPCS module.
This message indicates that the SYSVIEW NSS-PC has already been installed and that no changes were made that required a re-installation.
No valid module identifier could be located for the module named <modname>. This message will be followed by another message that displays the 1st 16 bytes of the module in hex. This is where the module identifier should have been located. Note the circumstances in which the error occurred and contact CA Technical Support.
This message displays the 1st 16 bytes of a module whose module identifier information was not valid. This message is preceded by a message that displays the name of the module. Note the circumstances in which the error occurred and contact CA Technical Support.
The module named <modname> is required to be located in LPA and it was found to be there.
The module named <modname> is required to be located in LPA. It was loaded to LPA because it was not found already in LPA.
A module named in a previous message was found to have an invalid release and/or build number. This message shows the release and build found and the release and build required.
The module name <modname> was found to have an invalid release and/or build number. This message is followed by a message that displays the release and build found and required.
This message displays information about the NSS-PC (Non SpaceSwitch-PC) installation service routine. The data displayed is:
This message displays the DD name from which the modules will be loaded.
Informational only.
An attempt to open the ddname <ddname> failed.
A BLDL issued to search for the module named <modname> in the ddname <ddname> returned a module-not-found return code.
A BLDL issued to search for the module named <modname> in the ddname <ddname> returned an I/O error return code.
A LOAD macro issued to load a module named <modname> failed with abend code <abncd>
The CAAT (CAAnchorTable) was not found.
The dynamic installation of the NSS-PC (NonSpaceSwitch-PC) does not support a task library DDname of <ddn>. Only a task library ddname of STEPLIB or JOBLIB is supported. If there is no STEPLIB or JOBLIB task library DDname then the required modules will loaded from LINKLIST.
This is a diagnostic message generated by the NSS-PC dynamic installation routine. It displays the results of a BLDL macro issued for an NSS-PC module. The data displayed includes:
This is a diagnostic message generated by the NSS-PC dynamic installation routine. It displays the results of a LOAD macro issued for an NSS-PC module. The data displayed includes:
This is a diagnostic message generated by the NSS-PC dynamic installation routine. It displays the LINKLIST data set name and volser that the NSS-PC modules will be loaded from.
This is a diagnostic message generated by the NSS-PC dynamic installation routine. When a LINKLIST data set is the source of the module that must be loaded the data set needs to be dynamically allocated and this dynamic allocation failed.
This is a diagnostic message generated by the NSS-PC dynamic installation routine. It is issued before testing a tasklib DD name to see if it contains SYSVIEW modules.
The SYSVIEW SGAT (SystemGlobalAnchorTable) was either found or build at the address <addr>.
An attempt to get storage in ESQA for the SGAT (SYSVIEW SystemGlobalAnchorTable) failed.
The SYSVIEW SGAT (SystemGlobalAnchorTable) was not found.
The the NSS-PC (NonSpaceSwitch-PC) installation service routine named <modname> completed with return code <retcd>.
The module named <modname> was successfully loaded to LPA using the CSVDYLPA service but a subsequent search for the same module name using CSVQUERY failed to find the module.
A CSVQUERY macro issued for module <modname> failed with return code <retcd>.
The module named <modname> was defined, replaced, or already in the SGAT (SYSVIEW SystemGlobalAnchorTable).
This message displays the following information about a module:
A CSVDYLPA macro issued to load the module named <modname> to LPA failed. This message will be following by another message containing details about the failed CSVDYLPA macro.
A CSVDYLPA macro issued to load the module to LPA failed. This message displays the return code, reason code, and error codes. A preceding message displays the name of the module for which the CSVDYLPA failed.
This message indicates that an NSS-PC (NonSpaceSwitch-PC) module was replaced. This message is followed by another message that displays the details of the replaced module.
This message indicates that an NSS-PC (NonSpaceSwitch-PC) module was replaced because the assemble date and time of the module found in the load library was different from the module found in LPA.
The IMS logger intercepts have been initialized.
The IMS logger intercepts have been removed.
The IMS log capture intercepts have been initialized for the specified IMS subsystem.
The IMS log capture intercepts have been terminated for the specified IMS subsystem.
An attempt was made to start an IMS logger for an IMS subsystem. The global IMS logger environment has not yet been enabled or has previously failed. See prior messages.
An attempt was made to start an IMS logger for the specified IMS subsystem. This subsystem has been defined as not to be monitored. Logger initialization terminates.
An internal trace message used to indicate IMS logger performance statistics.
The IMS logger resource manager could not be established.
The IMS logger task is being automatically started for the IMS subsystem.
An IMS logger task was started. The IMS subsystem was not active.
An IMS logger task was started for a DB only subsystem.
An IMS logger task was started for an IMS release that is not supported.
The IMS logger intercepted have been activated for the specified subsystem.
The IMS logger intercept and task have been deactivated for the specified subsystem.
The IMS logger task attempted to use a dataspace that was not owned by the correct jobname.
The IMS logger task attempted to create a dataspace. The request failed.
An attempt to initialize the IMS logger intercepts failed. Also see message GSVX867E and GSVX868E.
An attempt to initialize the IMS logger intercepts failed. Also see message GSVX866E and GSVX868E.
An attempt to initialize the IMS logger intercepts failed. Also see message GSVX866E and GSVX867E.
The DC monitor was already active within the IMS subsystem. The logger could not be activated. The logger can be activated once the DC monitor has been turned off.
IMS logger trace and debugging message.
An IMS logger has been started with the task name <logger>. The logger name is invalid. The logger name must follow the naming convention IMSssid. The first three characters of the logger name must be IMS followed by the subsystem of the desired IMS.
The IMS log capture intercept has been terminated due to a failure. The IMS intercept is suspended and the IMS logger task is abended with a U0011 abend code.
A new IMS logger environment structure has been allocated during IMSDATA task initialization. This is an informational only message.
An error occurred during IMS Logger task initialization. The return code will supply additional diagnostic information. Contact CA Technical Support.
The IMS logger task for the IMS subsystem indicated has successfully initialized. This is an informational only message.
The IMS Logger task processing has terminated normally or abnormally. A completion code exceeding "4" indicates an abnormal condition.
The condition code will supply additional diagnostic information. Contact CA Technical Support.
The IMS logger task was requested to terminate from the main task. This is a normal condition when the main task is terminating or when a termination command was entered for the logger task.
The IMS subsytem indicated has terminated. Monitoring of this subsytem will be terminated.
The IMSSPOC command was routed to multiple clients, however some may not have responded. See the IMS Common Service Layer Guide and Reference for a description of the return and reason codes returned by the CSLOMI service.
The IMSLOGR dataspace is initialized and formatted.
The IMSLOGR will monitor the event types specified in the message for non-message driven BMP region types. Record processing is controlled by the IMSLOGR PARMLIB option PROCESS-DCBMP-TYPE.
The IMSLOGR will monitor the event types specified in the message for CICS DBT region types. Record processing is controlled by the IMSLOGR PARMLIB option PROCESS-DCDBT-TYPE.
IMS logger task trace and debugging message.
IMS logger task trace and debugging message.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
This message is sent as a WTO when a SYSVIEW session has started and the OPTIONS PARMLIB SessionBeginEndWtoMessage option is set to YES. A period (C'.') will be displayed as a placeholder character for any message variable that is unknown.
This message is sent as a WTO when a SYSVIEW session has ended and the OPTIONS PARMLIB SessionBeginEndWtoMessage option is set to YES. A period (C'.') will be displayed as a placeholder character for any message variable that is unknown.
In order to get information for the requested display, RMF must be active. Start RMF and try the command again.
In order to get information for the requested display, the user must be authorized to access RMF data through the RMF programming interface (ERB3XDRS).
An unexpected situation occurred while getting the data for the requested display. Try the command again.
A date range was entered that was not available. Enter a date in the range <startdate> to <enddate>.
A date range was entered that exceeds the maximum allowed by RMF. Enter a valid date range.
CPC data was not available for the requested system.
RMF could not obtain enough storage to gather all of the data. Increase the region size and try again.
RMF could not obtain data for the specified time and date. Change the time and date and try again.
RMF could not obtain data for at least one of the systems listed. Check the Message field for the reason.
The specified system name could not be found in the available data. Reissue the command with a different system name.
RMF could not retrieve the requested data due to a time gap. The message indicates the range of the missing data.
Informational message displaying information about the LOGR subsystem exit module.
Informational message indicating the OPEN event has been given control for the specified ddname and log stream.
The options specified via the SUBSYS= parameter.
If a JCL error occurs during conversion, the <ddname> will contain "SUBSYS=".
Statistics information about the records read from the log stream.
A record passed back to the calling program has been truncated. Check the DCB attributed of the log stream specified.
An error has occurred during a call to the specified macro.
The specific blkid or record has been read and passed back to the caller. The length of the record before and after record expansion is shown.
The available times read from the specified log stream.
message - 'Request start time '
'Oldest record found'
'Youngest record found'
The block IDs read from the specified log stream.
message - 'Oldest block ID read'
'Youngest block ID read'
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Internal debugging message. Contact CA Technical Support for more information if this message is displayed.
Internal debugging message. Contact CA Technical Support for more information if this message is displayed.
This is the SYSVIEW copyright message. The content of the message variables are:
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
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.
The task is terminating because it received a UNIX System Services SIGKILL# signal (signal 9).
Reserved
Reserved
Reserved
Reserved
This message is used to display the contents of the STATSMSG parmlib member. The STATSMSG parmlib member contains message text that is displayed on the console prior to the output of the command:
MODIFY <id>,STATUS
This message is used to display the contents of the STARTMSG parmlib member. The STARTMSG parmlib member contains message text that is displayed on the console during initialization of the SYSVIEW main, auxiliary, and user interface address spaces.
Informational only.
Informational only.
A request was made to issue an internal message externally to the console using the WTO macro. The internal message was embedded in this external message. Lookup the internal message identifier for additional information. The action character of this external message will be the same as the action character of the internal message identifier.
A request has been made to issue a message. The message ID is unknown or invalid. Note the <msgid> value and contact CA Technical Support.
|
Copyright © 2014 CA.
All rights reserved.
|
|