This chapter describes each CA TPX Operator message that can be issued to the system console, or to the log if using the batch environment.
This section contains the following topics:
The messages in this chapter can appear with one of the following message prefixes:
For example, the message
TPX106 READMEMB SYNAD ROUTINE UNACCEPTABLE ERROR
will appear in the log as
TPB106 READMEMB SYNAD ROUTINE UNACCEPTABLE ERROR
The following describes certain sub-ranges of the Operator messages:
These messages can be issued to the operator in response to either a z/OS MODIFY command (F) or a command issued using the operator interface. These messages are self-explanatory, usually indicating that you entered the command with improper syntax or parameter values.
You receive these messages when the product attempts to recover from an abend error.
Reason:
This message shows product copyright information.
Action:
None.
Reason:
The product has completed initialization processing.
Action:
Log on to the product.
Reason:
The product has loaded a System Options Table (SMRT) that doesn't correspond to the level of the rest of the system.
Action:
Delete or rename any SMRT from earlier levels and try again.
Reason:
The PARM field in the JCL contains invalid data.
Action:
Correct the JCL and restart the product.
Reason:
The VM GCS machine is not authorized.
Action:
Include the user ID for this service machine as an AUTHUSER in your GCS configuration.
Reason:
Either a subtask has abended or an unrecoverable error has been detected. The product abends with the detected abend code.
Action:
None.
Reason:
A STOP command (P) has been entered at the system console. (If this is message TPB030, a STOP command has been simulated by the batch component.)
Action:
None.
Reason:
The product could not read the profile records due to the specified reason.
Action:
See IBM's VSAM Administration guide for a description of the errors.
Reason:
GETMAIN for an initialization work area has failed.
Action:
Adjust the REGION parameter in the product's procedure.
Reason:
The member or file name of the VTAM major node has not been specified in the JCL PARM field.
Action:
Specify the correct VNODE parameter in the JCL and restart the product.
Reason:
The VNODE parameter is invalid.
Action:
Specify the correct VTAM major node name and restart the product.
Reason:
The product could not load the specified module, probably due to corruption of the load library. If the product requires the module, it will abend with an abend code of U001.
Action:
Correct the error and restart the product.
Reason:
VSAM returned a non-zero return code, or there are no user or profile records in the VSAM file. This message is accompanied by a U001 abend.
Action:
Correct the VSAM file and restart the product.
Reason:
You specified ACB reservation in the SMRT, and it completed successfully.
Action:
None. Informational.
Reason:
The APPL member does not contain any virtual terminal ACBs.
Action:
Make sure that the product is pointing to the correct member of VTAMLST and restart the product.
Reason:
The VNODE member was not found in the VTAMLST DD data set.
Action:
Correct the error and restart the product.
Reason:
The specified table was not found in the ADMIN files. If the SMRT or ACT tables are not found, the product abends. Otherwise, it continues running without the table.
Action:
Correct the error and restart the product.
Reason:
A MODIFY RPL has failed while accessing the ADMIN1 file.
Action:
See IBM's VSAM Administration guide for information on the return code for MODCB.
Reason:
The region size is too small.
Action:
Increase the region size and restart the product.
Reason:
The product could not close the ADMIN1 file.
Action:
See IBM's VSAM Administration guide for information on ACBERFLG values.
Reason:
The product could not open the ADMIN1 file. If the product is running in batch mode, the job will end with return code of 20. Otherwise the product will abend with the abend code U001.
Action:
If flag has a value of A0 check if the ADMIN1 and ADMIN2 files specified in the file definitions are VSAM files that contain no records. These files must be initialized by having at least one record REPROed to them.
If flag has the value of BC, make sure that the ADMIN1 and ADMIN2 files are specified in the file definitions as VSAM files.
If flag has a value of 80, check to see if the ADMIN1 and ADMIN2 files are missing from the file definitions. In this case, the IEC130I message is often present.
Otherwise, see IBM's VSAM Administration guide for information on ACBERFLG values.
Reason:
The default Profile at TPX startup is not found and the site is running with dynamic profiles. pppppppp is the profile name which is missing.
Action:
The TPX administrator may have to either add a new default profile or restore the ADMIN2 file from a backup which contained the default profile.
Reason:
The GETMAIN for the ACBs has failed.
Action:
Adjust the region size and restart the product.
Reason:
Conflicting specifications for VTAM-authorized path usage have caused an initialization error.
If the APF PATH field in the SMRT is set to N, then the SRBEXIT must also be set to NO for all virtual terminal definitions in the CA TPX VTAM node. If the APF PATH field is set to Y, then the SRBEXIT must be set to YES for all virtual terminal definitions in the CA TPX VTAM node, and the CB0VLOAD must be APF authorized.
Action:
Correct the parameters and restart the product.
Reason:
The product processed a blank record when it read the VTAMLST major node.
Action:
Make sure that there are no missing or incorrect virtual terminal ACBs in the VTAMLST major node. Either restart the product with the corrected major node or continue processing after warning any affected users.
Reason:
An I/O error occurred while the product was reading the VTAMLST data set.
Action:
Determine the cause of the error, correct it and restart the product.
Reason:
Y was specified for VTAM authorized path facility, but the load library is not APF authorized.
Action:
Either specify N for the VTAM authorized path facility or APF authorize the load library.
Reason:
The VTAM OPEN for the specified virtual printer ACB failed.
Action:
See IBM's VTAM Programming guide for information on ACBERFLG values.
Reason:
The VTAM SETLOGON for the specified virtual printer failed.
Action:
See IBM's VTAM Messages and Codes guide for information on return codes and feedback values.
Reason:
A GETMAIN for an initialization work area has failed.
Action:
Increase the region size and restart the product.
Reason:
No shared virtual terminal ACB has been specified.
Action:
Either update the VTAMLST and restart the product or, if no applications require a shared ACB, continue without it.
Reason:
The PRIMARY ACB could not be opened. Usually this occurs when the name has been incorrectly specified in the startup procedure, the node has not been activated, or the region is already active.
Action:
Take the following actions:
Reason:
Initialization cannot proceed because VTAM is not active.
Action:
Either start VTAM or cancel the product.
Reason:
Initialization cannot proceed because VTAM has not completed its initialization.
Action:
None.
Reason:
Initialization cannot proceed because the major node has not been activated.
Action:
Check the VTAMLST definition statement in the startup procedure. Make sure that the data set name and member specified in the statement are correct. If the statement is correct, vary the major node active.
Reason:
Initialization cannot proceed until VTAM completes cleanup of a previous CA TPX.
Action:
None.
Reason:
Initialization cannot proceed until VTAM indicates that it has made storage available.
Action:
None.
Reason:
This message is issued the first time a user signs on and an invalid return code is encountered from a user exit. Another message is issued to the log each time the product receives an invalid return code from a user exit.
Action:
Correct the exit before restarting the product.
Reason:
The product could not attach its subtasks.
Action:
Make sure that the load library has been loaded correctly and is accessible.
Reason:
An error occurred in SETLOGON processing.
Identifies the reason this request was made to VTAM. Value can be:
Part of initialization
Part of the ACTIVATE command process
Part of the QUIESCE command process
Indicates function requested. Values can be:
The SETLOGON OPTCD+HOLD request failed with return and feedback codes indicated by nnnn. Logon will not be possible.
The SETLOGON OPTCD=START request failed with return and feedback codes indicated by nnnn. Logon will not be possible.
The SETLOGON OPTCD=GNAMEADD request failed with return and feedback codes indicated by nnnn. Generic resource support may not be available.
Action:
See IBM's VTAM Programming Guide for information on return code and feedback values. If the problem persists, contact CA Technical Support.
Reason:
An unrecoverable failure has occurred reading a file.
Action:
None.
Reason:
The product could not open the ADMIN2 file.
Action:
See IBM's VSAM Administration Guide for ACBERFLG values.
Reason:
A QUIESCE command has been entered. The text variable has the following possible values and meanings:
FOR application
FOR ALL APPLICATIONS
If there are no sessions to quiesce, the variable status has the value COMPLETED; otherwise it has the value INITIATED.
Action:
None.
Reason:
This message, issued by the syntax checker, indicates console command acknowledgment. The acknowledgment is accompanied by unnumbered messages that are the replies associated with the message.
Action:
None.
Reason:
This message is issued by the syntax checker in response to any executive command request. The message confirms that the command has been passed successfully and that the requested action will be attempted (or, if the action is impossible, indicates why the action cannot be attempted).
Action:
None.
Reason:
This message, issued by the syntax checker, indicates that an unexpected error condition occurred during the processing of a command.
Action:
If the problem persists, contact CA Technical Support.
Reason:
The specified slot pool overflowed for the first time. This message appears only once for each slot pool. The checking that produces this message is done on an hourly basis. The nn value is the number of the slot pool (1 through 12). The location value can be either BELOW-THE-LINE or ABOVE-THE-LINE.
Action:
None.
Reason:
The specified slot pool nn contains an invalid length value of iiiii and should contain a value of eeeee.
Action:
When the location value is set to ABOVE, then use the TPXADMIN application to set the current SMRT table value on the TEN0103 (System Options Table Detail Panel) panel for the slot pool nn to a size of eeeee for above the line slot pools.
When the location value is set to BELOW, then use the TPXADMIN application to set the current SMRT table value on the TEN0102 (System Options Table Detail Panel) panel for the slot pool nn to a size of eeeee for below the line slot pools.
Reason:
The TPX call to initialize the health Checker interface failed. The #HCHECK INITIALIZE call failed with R15 hex value of xxxxxxxx and a hex reason code of rrrrrrrr.
The inability of TPX to utilize the Health Checker facility does not prevent TPX from providing its normal product services at a site.
Action:
Appendix B in the CA Health Checker Common Service User and Reference Guide 12.0 explains the return (R15) and reason (R0) codes for the call failure. The return and reason codes will provide you further guidance.
Reason:
TPX attempted to add a Health Check for module mmmmmmmm.The #HCHECK ADD-CHK call failed with R15 hex value of xxxxxxxx and a hex reason code of rrrrrrrr.
The inability of TPX to utilize the mmmmmmmm Health Check does not prevent TPX from providing its normal product services at a site.
Action:
Appendix B in the CA Health Checker Common Service User and Reference Guide 12.0 explains the return (R15) and reason (R0) codes for the call failure. The return and reason codes will provide you further guidance.
Reason:
The TPX call to terminate the health Checker interface failed. The #HCHECK TERMINATE call failed with R15 hex value of xxxxxxxx and a hex reason code of rrrrrrrr. The TPX call to terminate the Health Check interface normally occurs during product shutdown.
Action:
Appendix B in the CA Health Checker Common Service User and Reference Guide 12.0 explains the return (R15) and reason (R0) codes for the call failure. The return and reason codes will provide you further guidance.
Reason:
TPX attempted to issue a CHK-MSG call in Health Check module mmmmmmmm. The #HCHECK CHK-MSG call failed with R15 decimal value of cccc and a decimal reason code of rrrr.
The inability of TPX to utilize the mmmmmmmm Health Check routine does not prevent TPX from providing its normal product services at a site.
Action:
Appendix B in the CA Health Checker Common Service User and Reference Guide 12.0 explains the return (R15) and reason (R0) codes for the call failure. The return and reason codes should guide your actions.
REASON:
TPX Health Check module mmmmmmmm ended with a non-zero return code. The #HCHECK routine mmmmmmmm will no longer run in the TPX address space. #HCHECK routine mmmmmmmm exited with R15 decimal value of cccc (HCE_RETCODE) and a decimal reason code of rrrr (HCE_RSNCODE).
The inability of TPX to utilize the mmmmmmmm Health Check routine does not prevent TPX from providing its normal product services at a site.
ACTION:
Appendix B in the CA Health Checker Common Service User and Reference Guide 12.0 explains the return (R15) and reason (R0) codes for the call failure.
The HCE_RETCODE return and HCE_RSNCODE reason codes should guide your actions. TPX support personnel should examine the module logic to see why module mmmmmmmm set these codes.
Reason:
The log has been dynamically allocated or reallocated successfully.
Action:
None.
Reason:
The z/OS/JES deallocation routines could not release the log for immediate printing.
Action:
None.
Reason:
A dynamic allocation request for the log data set has failed. The product will attempt to reopen the log.
Action:
None.
Reason:
The product could not open the log data set.
Action:
Check your JCL, System Options Table (SMRT) log class, and JES sysout printing options for the log. The product will continue to function without the log, but an immediate restart with a valid log is strongly advised.
Reason:
A spinoff request was issued but the log class was not specified in the System Options Table (SMRT). You cannot use the log spinoff facility.
Action:
Code a log class and (optionally) a LOGDEST in the SMRT and restart the product.
Reason:
The trace print utility could not open the print data set.
Action:
None.
Reason:
The trace print utility could not process the trace data set because the data set was not formatted.
Action:
Format the trace data set, restart TPX, perform the trace again, and rerun the print utility.
Reason:
The external trace is not available for this execution of the product for the specified reason. This message is the equivalent of the format utility message.
The product will continue to run, but the external trace will not function.
Action:
Correct the JCL and restart the product.
Reason:
The XTRACE DD statement refers to a data set that is not a direct access device.
Action:
Correct the DD statement and rerun.
Reason:
The XTRACE DD statement does not exist.
Action:
Add the DD statement and rerun.
Reason:
The product has used the default blocksize because no blocksize was specified on the XTRACE JCL.
Action:
None.
Reason:
The trace file has been initialized and consists of number physical blocks.
Action:
None.
Reason:
The trace formatter requires a direct access data set.
Action:
Recreate the trace file as a direct access data set.
Reason:
The format utility could not open the data set.
Action:
Determine and correct the cause of the error and try again.
Reason:
The product is waiting to connect to the file server on the specified CA‑L‑Serv subsystem.
Action:
Start CA‑L‑Serv if you have not already done so.
Reason:
The product cannot connect to the CA‑L‑Serv file server and is abending.
Action:
Start CA‑L‑Serv if you have not already done so. Make sure you specified the correct CA‑L‑Serv subsystem name on the DD statement in the CA TPX or CA‑STX startup procedure.
Reason:
The product cannot open the specified file.
Action:
Take the following actions:
Reason:
The product cannot open the specified file.
Action:
Check the CA‑L‑Serv portion of the CA Common Services documentation for a description of the return code and the VSAM guide for a description of the ACBERFLG. Call CA Technical Support if you cannot solve the problem with these descriptions.
Reason:
The entire DD statement is missing from the product startup procedure.
Action:
Add the appropriate DD statement or check the existing one and correct it.
Reason:
CA TPX determined that CA-L‑Serv is already managing a file by this name, so it cannot access the file. dddddddd is the ddname that references the file.
Action:
Correct the JCL so CA TPX will access the file through CA‑L‑Serv, or remove the file from CA-L‑Serv control. Restart CA TPX.
Reason:
When TPX starts, the TPXMAIL task calls TPXUMAIL exit at call point 36. If the exit compatibility interface available through CA Technical Support is used and if it detects that it has not been linkedited with a csect called TPXUBROD, it issues this message and clears the address of itself in the SMRT. It will never be called again. This message is echoed to the log immediately after the TPXL2222 message.
Action:
Correct the error and recycle the product.
Reason:
The specified user received a message and used PF3 to store the message. When the Mail server tried to store the message, one of the VSAM macros attempted actually failed. This message is followed by message TPX678.
Action:
Correct the VSAM file error and recycle the product.
Reason:
A user received a message and used PF3 to store the message. When the Mail server tried to store the message, one of the VSAM macros attempted actually failed. This message contains a line from TENMSGL, which describes the error. MMMMMMMM is the TENMSGL identifier. TTTTTTTT contains the text of the message. This message is preceded by message TPX677, which identifies to which user this message applies. This is the same message that would have appeared on a user screen, if the VSAM error had occurred while the user was in the TPXMAIL internal session.
Action:
Correct the VSAM file error and recycle the product.
Reason:
Quiesce processing has completed for applid.
Action:
None.
Reason:
An abend with the specified code has occurred in the specified module and task. The product will attempt to recover from the error.
Action:
See the chapter "Abend Codes."
Reason:
A dump is being written to the specified data set, either the SNAP data set, with the specified ID of id, or the system dump data sets SYS1.DUMPnn.
Action:
None.
Reason:
The product could not recover from the error and will abend with the code shown in message TPX990E or TPX990E.
Action:
None.
Reason:
The product will attempt to recover from the error.
Action:
None.
Reason:
The dump to SYS1.DUMPnn has failed with the specified return code. If ooo is 005, no SYS1.DUMP data set was available. Most other return codes indicate installation system problems. The product will attempt to use the SNAP DD statement. Return codes are described in IBM documentation.
Action:
Verify that the dump data sets are available and that the STEPLIBs are APF authorized
Reason:
An abend condition occurred in the TN3270 IP interface. Recovery of the failing task is being attempted.
Action:
None.
Reason:
An abend condition occurred in the TN3270 IP interface. Recovery is not permitted; the task will be terminated. The IP interface may no longer be operational.
Action:
None.
Reason:
A dump of the TN3270 IP interface is being written to a system dump data set SYS1.DUMPnn.
Action:
None.
Reason:
A dump of the TN3270 IP interface has been successfully written to a system dump data set SYS1.DUMPnn.
Action:
None.
Reason:
An informational message about VSAM file integrity will be displayed. See message TPXL0999 in the chapter "Log Messages."
Action:
None.
Reason:
The product is checking for a valid LMP key in the CAIRIM component of CA Common Services.
Action:
None.
Reason:
This message shows the CPU serial number, the CPU model number, and the current system date in dd/mmm/yy format. Only one CPU serial number is shown, even when several serial numbers exist. This message is issued during LMP key checking.
Action:
None.
Reason:
This message shows you the status of the specified component's authorization statement for the local system.
Action:
Your response depends on the status of the authorization statement:
Reason:
You are authorized to use the product on this CPU.
Action:
None.
Reason:
The component's authorization statement expires on the specified date. If you stop the product after this date, you will not be able to restart it using the current authorization statement.
Action:
Contact CA to obtain a new authorization statement.
Reason:
You are authorized to use the specified option on this CPU. This message is issued for informational purposes only.
Action:
None.
Reason:
Authorization for the specified option expires on the date shown in ddmmmyy. If you stop the product after this date, you will not be able to restart the option using the current option authorization statement. This message is for informational purposes only.
Action:
Contact CA for a new authorization statement.
Reason:
Authorization for the specified option has expired since you started the product. After the product is stopped, the option will not restart with the current authorization statement. This message is issued for informational purposes only.
Action:
Contact CA for a new authorization statement.
Reason:
The product could not open the data set that contains authorization statements. It will not execute until the file and a valid authorization statement are read.
Action:
Correct the problem and restart the product.
Reason:
The product could not find a valid authorization statement in the local CPU. It will not initialize until you specify a valid authorization statement.
Action:
Verify that the authorization statement is specified correctly.
Reason:
The product cannot find a valid authorization statement for the local system. It will not initialize on this CPU.
Action:
Verify that the authorization statement is specified correctly.
Reason:
The CPU serial number has changed since the product was started, and it will cease to function.
Action:
Restart the product using the CPU serial number specified in the authorization statement.
Reason:
The product's authorization was last checked number days ago.
Action:
None.
Reason:
The authorization module has abended. The associated system abend code is shown in Sxxx.
Action:
Contact CA Technical Support.
Reason:
CA-LMP has not started or been initialized through CAIRIM statement in CA Common Services.
Action:
Correct problem and restart the product.
Reason:
Product failed authorization from CA-LMP.
Action:
Contact CA for valid LMP KEY for this Product.
|
Copyright © 2013 CA.
All rights reserved.
|
|