Reason:
There is a syntax error in one or more of the optional arguments, 'JID=', 'ADATE=', or 'ATIME='.
Action:
Correct the arguments and resubmit the job.
Examples
ADATE=mm/dd/yyyy
ATIME=hh:mm
JID=JOBnnnnn
Reason:
An error occurs while issuing an open ACB request. Code xx is returned in the ACB field ACBERFLG.
Action:
Consult the IBM VTAM Programmer manual for explanation on error for open of VTAM ACB, correct, and retry.
Reason:
An error occurs when issuing an OPENDST for the indicated logical unit. The return code, feedback code, and sense information are shown.
Action:
Consult the IBM VTAM Programmer manual for explanation on error for open for OPENDST, correct, and retry.
Reason:
An error occurs when issuing a SEND for the indicated logical unit. The return code, feedback code, and sense information are shown.
Action:
Consult the IBM VTAM Programmer manual for explanation on error for SEND to VTAM Device, correct, and retry.
Reason:
The logical unit indicates it is not a VTAM logical unit as reported by a value other than DEVLU being returned in the DEVTCODE field of the NIB after the OPENDST is completed.
Action:
Use a VTAM device.
Reason:
The task of successfully opening the VTAM ACB while processing the logical unit indicates that it is not possible to locate an available APPLID with the indicated value.
Action:
Either define the necessary APPLIDs to VTAM or specify an existing APPLID in the VPRTAPPL initialization parameter.
Reason:
An error occurs when issuing a SIMLOGON for the indicated logical unit. The return code, feedback code, and sense information are shown.
Action:
Correct the error and retry.
Reason:
The VTAM printer that is specified as xxxxxxxx is either not defined to VTAM or is busy longer than the retry limits specify in the VPRTRTRY and VPRTRINT initialization parameters.
Action:
Either use a printer that is defined to VTAM or (if the printer is already defined to VTAM) wait until it is not being used.
Reason:
The LOGMODE specified in the DEFine DEVice for logical unit xxxxxxxx is not available to VTAM.
Action:
Either make the LOGMODE available to VTAM, or specify a usable LOGMODE in the DEFine DEVice panel.
Reason:
This is a replication of a message generated at a terminal and can contain any numbered or unnumbered message. The format contains the VTAM Application Identified, the VTAM Terminal Identifier, the constant 'VI' (indicating VTAM) and a copy of the message text displayed to the terminal user.
Action:
The action depends on the message text; normally the terminal user could be required to perform some action or report a problem.
Example:
SARVAPI1 A03SARVT_TCPL0860_VT
SARDBI00 Database SAR.JCL does not exist
Reason:
A terminal session has been created (this message follows the 'Logon Request' and 'Terminal Connected' messages) and displays the terminal characteristics, that is, screen size and color/highlighting capabilities of the terminal session.
Action:
None. This message is informational.
Reason:
An unusable earlier version of shared common code has been detected. BASE shows the version detected, and REQ shows the version required.
Action:
Correct the error and retry. This can be done by putting the CA View LOADLIB ahead of EXPRESS, BALANCING, and/or ARISE LOADLIBs.
Reason:
The VTAM terminal has been successfully connected to the user subtask in the region. This message has a MSGLVL of NORM.
Action:
None. This is an informational message.
Reason:
The CA View program has ended normally. This message has a MSGLVL of NORM.
Action:
None. This is an informational message.
Reason:
A VTAM CLSDST to disconnect the terminal is now issued. This message has a MSGLVL of TRCE.
Action:
None. This message is informational.
Reason:
CA View detected a problem with the session bind parameters and has rejected the terminal logon. This message has a MSGLVL of ACTN.
Action:
Review the REJECT reason for the appropriate action.
Reason:
This message displays the bad bind image data rejected by message SARXDRV5. This message has a MSGLVL of ACTN.
Action:
Contact your VTAM systems programmer or CA Technical Support. This can be a VTAM definition problem.
Reason:
The incorrect screen size to bind data changes to conform to normal 3270 screen sizes. This message has a MSGLVL of NORM.
Action:
Contact your VTAM systems programmer. This can be a VTAM definition problem.
Reason:
The VTAM access method has requested closing the VTAM ACB, because of command processing or VTAM shutdown. This message has a MSGLVL of CRIT.
Action:
Contact your VTAM systems programmer.
Reason:
The system generated a message to inform you about the next standard backup cycle:
nnnn is the current database generation number.
Action:
None. This message is informational.
Reason:
The system generated a message to inform you of a pending delete:
Action:
None. This message is informational.
Reason:
The system generated a message to inform you of a pending delete:
nnnn is the number of reports which is deleted from the primary disk. If these reports are also being deleted from the tape and/or secondary disk, these counts are reflected in the SARVERO01 and/or SARVERO04 messages as well.
Action:
None. This message is informational.
Reason:
The system generated a message to inform you of a pending delete:
nnnn is the number of reports which is deleted from the secondary disk. If these reports are also being deleted from tape and/or primary disk, these counts are reflected in the SARVERO01 and/or SARVERO03 messages as well.
Action:
None. This message is informational.
Reason:
The system generated a message to inform you of a pending migration:
nnnn is the number of reports which are on the primary disk and are migrated to the secondary disk if the secondary disk is defined in this database.
Action:
None. This message is informational.
Reason:
The system generated a message to inform you of pending tape expirations:
xxxx is the number of tapes which is uncataloged and removed from the database.
yyyy is the number of tapes currently defined in the database.
Action:
None.
Reason:
The ERO Table Validation Utility cannot run a simulated backup cycle to verify the ERO settings and table because the initialization parameter EROOPT is set to NO.
Action:
The utility can be used to validate an ERO Table pointed to by the SARPATAB DD Statement if the execution parameter is set to PARM=',TABLE'. If a full backup cycle validation is desired, then the ERO Option must be turned on in the database.
Reason:
A VTAM error has occurred processing a request from the VTAM interface. The RC= shows the problem return code. This message has a MSGLVL of ACTN.
Action:
The action to take depends on the session status and type of error. Most errors show communications problems.
Reason:
The VTAM user subtask has ended normally or with an abend condition. This message has a MSGLVL of NORM.
Action:
None. This is an informational message.
Reason:
The VTAM logon request has been received, CA View attaches the user subtask to support the user. This message has a MSGLVL of INFO.
Action:
None. This message is informational.
Reason:
The VTAM logon request was rejected, the message shows the reason. This message has a MSGLVL of ACTN.
Action:
Review the REJECT reason for the appropriate action.
The message containing ***REJECTED-NO XMCT AVAILABLE is issued when the maxuser threshold has been reached and no other XMS region is available for use. XMS checks two criteria for determining whether the maxuser threshold per XMS region has been exceeded.
These are as follows:
Storage constraints govern the maximum users supported by an XMS region. As a rule, XMS regions must have 7 to 8 MB of below the line storage available and 10 MB plus 1 MB for each 3 users of above the line storage available.
Reason:
The VTAM logon request was not accepted by this region, the request is passed to the next CA View region for processing. This message has a MSGLVL of NORM.
Action:
None. This is an informational message.
Reason:
A VTAM session has been lost for this terminal. This message has a MSGLVL of NORM.
Action:
VTAM has disconnected the terminal, possibly due to a terminal or network outage.
Reason:
A VTAM CLSDST to disconnect the terminal is issued. This message has a MSGLVL of INFO. This message occurs at the normal end, or an ABEND, of the VTAM session.
Action:
None. This message is informational.
Reason:
The VTAM terminal session has been forced off successfully. This message has a MSGLVL of INFO.
Action:
None. This is an informational message.
Reason:
An attempt is made to retrieve the logical views for a report, but no logical views are defined for the report.
Action:
None. Only the native view of the report is accessible.
Reason:
An error occurs while issuing an open ACB request. Code xx is returned in the ACB field ACBERFLG.
Action:
Consult the IBM VTAM Programmer manual for explanation of errors for open of VTAM ACB; correct, and retry.
Reason:
An error occurs when issuing an OPENDST for the indicated logical unit. The return code, feedback code, and sense information are shown.
Action:
Consult the IBM VTAM Programmer manual for explanation of errors for open for OPENDST; correct and retry.
Reason:
An error occurs when issuing a SEND for the indicated logical unit. The return code, feedback code, and sense information are shown.
Action:
Consult the IBM VTAM Programmer manual for explanation of errors for SEND to VTAM Device; correct and retry.
Reason:
The logical unit indicates it is not a VTAM logical unit as reported by a value other than DEVLU being returned in the DEVTCODE field of the NIB after the OPENDST is completed.
Action:
Use a VTAM device.
NO AVAILABLE APPLIDS, LU=XXXXXXXX, APPLID=XXXXXXXX
Reason:
The task of successfully opening the VTAM ACB while processing the logical unit indicates that it is not possible to locate an available APPLID with the indicated value.
Action:
Either define the necessary APPLIDs to VTAM or specify an existing APPLID in the VPRTAPPL initialization parameter.
Reason:
An error occurs when issuing a SIMLOGON for the indicated logical unit. The return code, feedback code, and sense information are shown.
Action:
Correct the error and retry.
Reason:
The VTAM printer specified as xxxxxxxx is either not defined to VTAM or is busy longer than the retry limits specify in the VPRTRTRY and VPRTRINT initialization parameters.
Action:
Either use a printer defined to VTAM or (if the printer is already defined to VTAM) wait until it is not being used.
Reason:
The LOGMODE specified in the DEFine DEVice for the logical unit xxxxxxxx is not available to VTAM.
Action:
Either make the LOGMODE available to VTAM, or specify a usable LOGMODE in the DEFine DEVice panel.
Reason:
A VTAM OPEN or CLOSE has not completed successfully. The VTAM signon task is shut down. This message has a MSGLVL of CRIT.
Action:
Contact your VTAM systems programmer.
Reason:
A VTAM OPEN or CLOSE code failure reason. This message has a MSGLVL of CRIT.
Action:
Contact your VTAM systems programmer.
Reason:
A VTAM MODCB macro has failed, the VTAM session cannot be initialized, and the EC1VTSGN program is shut down. This message has a MSGLVL of CRIT.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
VTAM signon initialization is completed. VTAM users can now sign onto the region. This message has a MSGLVL of NORM.
Action:
None. This is an informational message.
Reason:
The console operator has stopped the region, but users are still active. The VTAM signon task waits for the users to complete processing. This message has a MSGLVL of NORM.
Action:
None. This message is informational.
Reason:
The indicated VTAM routine loaded and attached to the VTAM ACB exit list. The release and assembly date and time are displayed. This message has a MSGLVL of INFO.
Action:
None. This is an informational message.
Reason:
A subtask abend has been detected and the session now be cleaned up. This message has a MSGLVL of ACTN.
Action:
None. This message is informational.
Reason:
The terminal shown has not had a transaction for a period exceeding the time specified in the LONGWAIT= parameter. This message has a MSGLVL of ACTN.
Action:
If CANCEL=YES is specified for the region, the user is canceled. Otherwise the task status is changed to LONGWAIT.
Reason:
The open has failed for the application program ACB.
Action:
Verify that the SARVTAM APPLID is activated. Normally, inactivating and re-activating the SARVTAM APPLID fixes the problem.
Reason:
The VTAM online retrieval task in now ready for users to log on to it.
Action:
None. This is an informational message.
Reason:
This message is in response to the successful quiesce request.
Action:
None. This is an informational message.
Reason:
The application is terminating.
Action:
None. This is an informational message.
Reason:
An invalid operator command has been issued.
Action:
Reenter the operator command in its correct form.
Reason:
The user subtask has abended. Consult message SARVTA14 for further information.
Action:
None. This is an informational message.
Reason:
The losterm exit has been invoked for the session with the specified LU name. The session is terminated.
Action:
None. This is an informational message.
Reason:
VTAM has been terminated with a Z NET or V NET,INACT command. VTAM online retrieval is terminated.
Action:
After VTAM has been started again, start the VTAM online retrieval task.
Reason:
A session with the specified logical unit has started.
Action:
None. This is an informational message.
Reason:
The session with the specified logical unit has terminated normally.
Action:
None. This is an informational message.
Reason:
The specified VTAM request has failed.
Action:
Reference the return and feedback codes to determine the cause of the error.
Reason:
An attempt to recover from a previous error has failed.
Action:
Consult the message for the previous error.
Reason:
The DFASY exit has been entered for the specified logical unit.
Action:
None. This is an informational message.
Reason:
The user subtask has abended. A completion code of 306000 occurs when the CA View load library is not authorized. The session with the user is terminated.
Action:
None. This is an informational message.
Reason:
An exceptional condition is reported by VTAM.
Action:
This message has a MSGLVL of NORM. This can occur for a number of reasons. For assistance, contact Technical Support at http://ca.com/support.
Reason:
An exceptional condition is reported by VTAM.
Action:
This message has a MSGLVL of NORM. This can occur for a number of reasons. For assistance, contact Technical Support at http://ca.com/support.
Reason:
An exceptional condition is reported by VTAM.
Action:
This message has a MSGLVL of NORM. This can occur for a number of reasons. For assistance, contact Technical Support at http://ca.com/support.
Reason:
The control statement does not begin with a slash (/), or a percent sign (%). The control statement is ignored.
Action:
Correct the statement.
Reason:
The control statement contains an invalid SYSOUT ID. The control statement is ignored.
Action:
Correct the statement.
Reason:
The control statement contains an invalid parameter. The parameter is ignored.
Action:
Correct the statement.
Reason:
Too many parameters are specified for the SYSOUT ID.
Action:
Reduce the number of parameters on the control statement.
Reason:
The Exceptional Conditions checking table parameters have been reloaded.
Action:
None. This is an informational message.
Reason:
The control statement contains two or more of the mutually exclusive FIRST, LAST, and HIGH parameters.
Action:
Correct the entry in the Exceptional Conditions checking table (SARXCTAB) and reload the table.
Reason:
The XMS user subtask has terminated abnormally. This message has a MSGLVL of NORM.
Action:
None. This is an informational message.
Reason:
The XMS user subtask has terminated normally. This message has a MSGLVL of NORM.
Action:
None. This is an informational message.
Reason:
The XMS user subtask has terminated and an internal error was detected cleaning up the session. This message has a MSGLVL of NORM.
Action:
Contact CA Technical Support.
Reason:
A CA View program has terminated, and a dump was generated. In this message, blk specifies the control block CA View expected but did not receive (usually IFB, SFB, XFB, or DBB). It could be suffixed with a number indicating which test point in the program detected the problem.
Action:
Send the dump to CA Technical Support. Restart whatever program was terminated. If the problem recurs, run SARDBASE VERIFY on the database. For assistance, contact Technical Support at http://ca.com/support.
SARXOC04 NO QUALIFIED REPORTS FOR CROSS-REPORT INDEX
Reason:
No reports, indexing information or both are found in the database for the selected cross report index name and filtering criteria.
Action:
Select another cross report index name or change the filtering criteria.
Reason:
External Print sample program SARXPDSK has been installed and has queued a report to the named data set.
Action:
None. This is an informational message.
Reason:
XMS signon request received, CA View attaches the user subtask to support the user.
Action:
None. This message is informational.
Reason:
XMS signon has detected an internal error during processing. This message has a MSGLVL of ACTN.
Action:
Contact CA Technical Support.
Reason:
XMS found the count of active users in the XMEMCNTL was bad and corrected it. This message indicates that CA View has lost track of the correct number of users in the region. This message has a MSGLVL of ACTN.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
XMS has not been able to locate its ASCB control block. This message has a MSGLVL of ACTN.
Action:
Contact CA Technical Support.
Reason:
A subtask abend has been detected and the session is now cleaned up. This message has a MSGLVL of ACTN.
Action:
None. This message is informational.
Reason:
The terminal shown has not had a transaction for a period exceeding the time specified in the LONGWAIT= parameter. This message has a MSGLVL of ACTN.
Action:
If CANCEL=YES is specified for the region, the user is canceled. Otherwise, the task status is changed to LONGWAIT.
Reason:
SARXTD has been started to change or turn off extensions.
Action:
Reply Y to authorize the change, or N to prevent the change.
Reason:
An invalid reply has been given to message SARXTD01.
Action:
Reply correctly to message SARXTD01.
Reason:
The operator has replied N to message SARXTD01.
Action:
If authorization has been erroneously denied, start SARXTD again.
Reason:
SARXTD has been started without a DD statement for the job accounting data set.
Action:
Verify that job accounting is not to be in effect.
Reason:
The job accounting data set can only have one extent.
Action:
Recreate the job accounting data set.
Reason:
The PARM field contains invalid syntax starting with the first character displayed.
Action:
Correct the PARM field and start SARXTD again.
Reason:
Data set security is in effect for all data sets whose names begin with the specified prefix.
Action:
None. This is an informational message.
Reason:
Job accounting information is maintained in the specified accounting data set.
Action:
None. This is an informational message.
Reason:
The automatic report archival feature is active and the specified archival criteria is in effect.
Action:
None. This is an informational message.
Reason:
Data set security is no longer in effect.
Action:
None. This is an informational message.
Reason:
Job accounting data is no longer being maintained.
Action:
None. This is an informational message.
Reason:
The automatic report archival feature is no longer in effect.
Action:
None. This is an informational message.
Reason:
When a systems extension is started and contains a NOTERM DD statement, the system extensions task remains active and responds to operator commands. The MODIFY command that is entered at the operator console is invalid.
Action:
The valid operator commands that can be entered are: OFF, OFFSEC, OFFACT, OFFARA, STATUS, and STOP. The system extensions task automatically terminates when the OFF or STOP commands are entered, or when all the system extension facilities have been disabled.
Reason:
A system extensions task is already active for the subsystem identifier. Each system extensions task is assigned a one-character subsystem identifier, which can be defined by using the SUBSYSx DD statement, and a system extensions task currently is executing with the same identifier. Execution of the recently started task is terminated.
Action:
If an additional system extension task is required, specify a unique subsystem identifier by using the SUBSYSx DD statement. Otherwise, verify that the previously started systems extensions task specifies the desired parameters. If not, terminate the previously started systems extensions task, and start the new task.
Reason:
Informational message indicating that all facilities for the system extensions task have been disabled and the systems extensions task is terminating.
Action:
None. This message is informational.
Reason:
An attempt has been made to execute SARXTD as other than a started task.
Action:
Execute SARXTD by using the START command.
Reason:
SARXTD has determined that it lacks required APF-authorization. SARXTD requires APF-authorization to modify the various operating system interfaces dynamically.
Action:
Ensure that SARXTD resides in an APF-authorized load library. Alternatively, SARXTD can be placed in a linklist library provided LNKAUTH=LNKLST has been specified or allowed to default in the active IEASYSxx member of SYS1.PARMLIB. Under no circumstances must SARXTD be placed in any of the link pack areas.
Action:
See the IBM documentation for the IOSCAPU return code indicated in the previously issued SARXTD20 message.
Action:
See the IBM documentation for the IOSCAPU return code indicated in the previously issued SARXTD21 message.
Reason:
The SARXTD is being restarted and Automatic Report Archival is active.
Action:
If the restart is being performed to refresh the Automatic Report Archival SVC, the previous execution of the task was not properly terminated. Reply 'Y' to the SARXTD01 message, and then issue a "F SARXTD,OFF" (if running with NOTERM) or "S SARXTD,PARM=OFF" (if the task normally terminates after activation), and re-issue the start command to refresh the Automatic Report Archival SVC.
|
Copyright © 2013 CA.
All rights reserved.
|
|