This chapter describes the messages that CA TPX may write to the data set described by the LOG DD statement. Messages are written at initialization time and during normal processing. The log processor manages and formats log message requests asynchronously with other processes but synchronously with other log requests. Log messages are written in the order they are presented to the log writer.
This section contains the following topics:
Log messages have the following format:
TPyLnnnn mm/dd/yy.ddd hh:mm:ss.th text
where:
Carries the following values:
If issued in the online environment.
If issued in the batch environment.
Some messages can be issued in both environments.
Indicates that this is a log message.
Indicates the date the message is issued.
Indicates the time of day.
The indicated time is the time the message was processed by the log writer and may be later than the event that generated it. This is especially true of initialization messages that are not processed until the subtask has initialized.
Operator messages with the TPX prefix (issued in the online environment) and the TPB prefix (issued in the batch environment) are also copied to the log. These messages are documented in the chapter "Operator Messages."
Log messages are presented here in numerical order, regardless of message prefix.
Reason:
This message is issued at startup time to identify the version, release, and service level of CA TPX.
Action:
None.
Reason:
The product is executing in the specified environment with the specified local mode of operation.
Possible environments are:
Possible operating modes are:
Action:
None.
Reason:
This is a diagnostic message identifying each module that is loaded during initialization and the date and time of assembly. Where no module statistics are available, either no data is displayed or the text <USER EXIT> may appear. This message may be particularly useful in verifying the assembly date of any installation-written user exits.
Action:
None.
Reason:
The specified VTAMLST major node contains the virtual terminal and virtual printer definitions. This is the member/file name in the data set identified by the VTAMLST DD statement or the VNODE PARM field value. A listing of the major node definition may follow this message.
Action:
None.
Reason:
This message is issued after the primary ACB has been opened. It identifies the global and local network name for the primary ACB and, where possible, identifies the release of VTAM and the local SSCP, HOST, and NETWORK names.
Action:
None.
Reason:
This message is issued after you enter the TPXOPER VTADD command to add virtual terminal definitions. The value of text is one of the following:
VIRTUAL TERMINAL ADDITIONS PROCESSING DONE INVALID ENTRY IN VTAMLST MEMBER SRBEXIT/FASTPATH CONFLICT. PROCESSING STOPPED STORAGE NOT AVAILABLE. PROCESSING STOPPED ERROR GENERATING NEW TERMINAL. PROCESSING STOPPED INVALID OR NO MEMBER SPECIFIED. PROCESSING STOPPED NO NEW VIRTUAL TERMINALS ADDED. PROCESSING DONE VTAMLST ADDITIONAL NODE nnnnnnnn
Action:
None.
Reason:
This message is issued at startup time to identify the CA TPX jobname of JJJJJJJ, running version X.X at the service level of LL.
Action:
None.
Reason:
This is an informational message. nnnn identifies the number of applications defined as type Group.
Action:
None.
Reason:
The specified user has either signed on or off the specified terminal. The event variable has a value of either SIGNON or SIGNOFF.
Action:
None.
Reason:
The specified virtual terminal session has ended or been killed. The virtual terminal session is identified by the VTAM application ID, the virtual terminal used, the session ID, and the associated user ID. The status variable has a value of ENDED or KILLED.
Action:
None.
Reason:
A terminal session has ended.
Action:
None.
Reason:
The specified user has logged off from the product.
Action:
None.
Reason:
The specified terminal for user userid has timed out. The value of type specifies 1 for a first stage timeout, 2 for a second stage timeout, or L for a logo timeout.
The value of goal specifies the goal timeout interval for the terminal. The value of actual specifies the actual timeout interval. The value of action specifies the command issued as a result of the timeout.
Action:
None.
Reason:
The specified session for user userid has timed out.
Action:
None.
Reason:
A session cannot be started because there is a storage overload condition.
Action:
None.
Reason:
The specified user has issued an operator command.
Action:
None.
Reason:
The specified user has modified storage from an operator session.
Action:
None.
Reason:
A VTAM TERMSESS macro has been issued to terminate a virtual printer session.
Action:
None.
Reason:
A VTAM TERMSESS macro has been issued to terminate a physical printer session.
Action:
None.
Reason:
The product has received a VTAM UNBIND from a virtual printer, indicating that the virtual printer session has ended.
Action:
None.
Reason:
A passthrough print request has been completed.
Action:
None.
Reason:
A physical printer session was ended and the software was notified by the Network Services exit (NSEXIT). This usually means that the session with the printer was ended by the VTAM "vary inactive" command with the "force" option.
Action:
None.
Reason:
The product received an invalid return code from the SIGNON/SIGNOFF user exit.
Action:
Correct the exit and restart the product.
Reason:
The specified terminal has logged off from the product.
Action:
None.
Reason:
The product has detected an overrun condition on session sessionid for user userid and has issued a RESETSR to inhibit any further input and will terminate the session.
Action:
None.
Reason:
The product could not locate the profile in the ADMIN2 file. The profile was requested for a user at signon time.
Action:
None.
Reason:
ACB selection has started. This message is issued during virtual terminal ACB selection processing when the ACB selection trace has been requested.
Action:
None.
Reason:
ACB trace is active and the specified mask is being used for the subsequent search.
Action:
None.
Reason:
ACB trace is active and has selected a virtual terminal ACB mask that matches the user's real terminal name.
Action:
None.
Reason:
ACB trace is active and is testing a virtual terminal ACB for eligibility.
Action:
None.
Reason:
ACB trace is active and has found a virtual terminal ACB that matches the requested mask.
Action:
None.
Reason:
The product has started a PASS session for the specified user and application session.
Action:
None.
Reason:
The product has selected the specified ACB for the specified user and application.
Action:
None.
Reason:
The specified application has requested a session with the virtual printer. The address is the address of the session control block for the session.
Action:
None.
Reason:
No eligible virtual terminal is available to start a session. If no user ID is available, the message shows the real terminal name.
Action:
Check the following to determine why an ACB was unavailable:
Application and virtual terminal definitions are described in detail in the Installation Guide and the Programming Guide.
You may want to run an ACB trace with the operator TRACE command, as described in the Operator Guide.
Reason:
No virtual terminal is available for the specified session.
Action:
See the suggested action for message TPXL0037.
Reason:
A session limit has been exceeded. The session that the product is currently starting will be aborted. The type variable specifies the type of limit (USER or APPLICATION) and the name variable specifies either the user ID or the real terminal name.
Action:
None.
Reason:
The product has rejected a session request because the user is pending a signoff.
Action:
None.
Reason:
The product has rejected an attempt to establish a session between a virtual terminal ACB and the primary ACB.
Action:
None.
Reason:
The product has rejected a logon request from a terminal that is already logged on.
Action:
None.
Reason:
The product received a terminal query reply that contains an invalid structured field length value. The query reply is rejected and the terminal is treated as unable to be queried.
Action:
None.
Reason:
The product does not recognize the type of terminal with which it is in a session and cannot determine if the device is a 3278, a 3279, a 3179, and so on. This message is for informational purposes only.
Action:
None.
Reason:
The terminal session parameters do not contain any standard screen size.
Action:
None.
Reason:
The product has received a bind from an application that is incompatible with the connected terminal.
Action:
None.
Reason:
The terminal that is attempting to log onto CA TPX is not defined as an LU0, LU1, or LU2.
Action:
Correct the LU definition in VTAM for this terminal.
Reason:
The product has entered a save area expansion.
Action:
None.
Reason:
The product has encountered an error during screen image processing. This message might be followed by a User 350 abnormal termination. If ERROPT=RECOVER is coded in the SMRT, processing will continue.
Action:
None.
Reason:
The LOSTERM exit was invoked for the specified session for the specified reason. If a LOSTERM reason code greater than 36 is encountered, the code is printed in hexadecimal. The following reasons may appear:
UNRECOVERABLE TERMINATION
TERMINATION COMPLETE
UNCONDITIONAL TERMINATION
SESSION FAILURE
CONDITIONAL TERMINATION
BUFFER SHORTAGE REPORTED
Action:
None.
Reason:
NSEXIT has been scheduled on the specified session with the specified REASON and SENSE data. The following is a list of values and corresponding meanings that the variable type can have:
A CLEANUP RU (810629) was received. The session will be cleaned up.
A NOTIFY RU (810620) was received. The session will either be terminated or an appropriate message will be issued to the end user.
An NSPE (010604) is an error caused by VTAM being unable to associate a session with its correlated user. This error may occur with the following situation:
An unexpected RU has been encountered by the exit. Instead of the PLU and SLU, the RU type will be printed in hexadecimal. This message only appears for RU types that are not:
CLEANUP = 810629
NOTIFY = 810620
NSPE = 010604
The following lists possible values that the variable reason can have and their corresponding meanings:
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
The specified terminal has been released because another application issued a SIMLOGON OPTCD=(Q,RELRQ) command and the terminal is considered eligible for release.
Action:
None.
Reason:
The product has rejected the bind from an application. The reason variable can have one of the following values:
- SBSREQS NOT ON - - ISSUES CLSDST PASS - ACT= act-name, PLU=applid - AMAPSB NOT AN SB - ACB= vtrm-ID, PLU=applid - SBACTP .NE. ACTADDR - BIND RECEIVED FOR NONSLU ACB - UNSUPPORTED PRINTER TYPE - PPS SUPPORT NOT AUTHORIZED - VPS VIRTUAL PRINTER NOT AVAIL. - PRINTER NOT AVAIL. OR INCOMPATIBLE ACB=vprtrID : - MAXSESS REACHED . . . PPS SESSION REJECTED - APPL QUIESCED . . . PPS SESSION REJECTED - NO ACT ENTRY FOUND - ACB= vtrm-ID, PLU=applid - NO CPS ON ACT - NO SB FOUND FOR SIMLOGON/ACQUIRE - ACB= .vtrm-ID PLU=applid - NO SB FOUND FOR CLSDST PASS - ACB= vtrm-ID PLU=applid - UNEXPECTED BIND RECEIVED, SBACPS NOT ON - vtrm-ID PLU=applid - SBAPPID .NE. ACTNAME - SBAPPID= vtrm-ID ACTNAME= act-name - SIMLOGON/ACQUIRE REJECTED - PLU= applid ACB=vtrm-ID - BAD BIND IMAGE - VIRTUAL PRINTER MASK RESOLVES TO BLANKS - PRINT DEST. TABLE HAS NO ENTRIES - REJECTED BY TPXUPSEL EXIT - NO PRINTER AVAILABLE - VIRTUAL PRINTER NOT DEFINED IN PRINT DEST. TABLE
Action:
If the reason is not clear to local CA TPX support, contact CA Technical Support for further assistance.
Reason:
The specified printer cannot be released because it is not in session with the product.
Action:
None.
Reason:
The product could not close the note file.
Action:
See IBM documentation on VSAM administration for information on ACBERFLG values.
Reason:
The notepad has encountered a VSAM error.
Action:
See IBM documentation on VSAM administration for information on return codes and reason codes.
Reason:
The product has issued the RESETSR macro because the application was flooding the software with data. The product will terminate the session.
Action:
None.
Reason:
The product received a data RU with a length greater than 65K.
Action:
None.
Reason:
The instruction is being executed in the specified ACL/E program.
Action:
None.
Reason:
This message is issued at the end of an ACL/E program if the OPTION FLOW was on. The meaning variable can have these values:
NORMAL COMPLETION -operation- OPERATION CONTAINED AN INVALID OPERAND n -operation- OPERATION ENCOUNTERED OUT-OF-RANGE CONDITION SCRIPT EXCEEDED INSTRUCTION EXECUTION LIMIT NO OPCODE ENCOUNTERED IN STATEMENT STATEMENT CONTAINS AN INVALID OPCODE -DELETE- OPERATION ENCOUNTERED OUT OF RANGE CONDITION -EOF- TRIED DOING EOF ON A PROTECTED FIELD ACLPGM STARTED ANOTHER ACLPGM FOR INVALID SESSION -DISPLAY- PANEL VIOLATES NAMING CONVENTIONS -DISPLAY- PANEL NAME NOT FOUND IN LIBRARY -DISPLAY- PANEL NOT BUILT DUE TO DEFINITION ERRORS -COMMAND- OPERAND-1 IS NOT A VALID TPX COMMAND -*DEFINE- OPERAND-n INVALID -*DEFINE- OPERAND-2 IS NOT NUMERIC -*DEFINE- OPERATION FAILED -*DELETE- OPERAND-1 INVALID -*DELETE- OPERATION FAILED OPERATION CONTAINED AN INVALID OPERAND 1 -OPTION- TIMEOUT VALUE IS NOT NUMERIC -OPTION- TIMEOUT ADDRESS IS NOT A VALID LABEL -OPTION- OPERAND-1 INVALID -SET- INVALID ROW/COLUMN SPECIFICATION OPERAND-1 INVALID OPERAND-1 IS NOT NUMERIC OPERAND-2 INVALID -NOTIFY- OPERAND-1 IS NOT A VALID SESSION NAME -NOTIFY- OPERAND-1 IS NOT AN ACTIVE SESSION ****** ACL/E FUNCTIONS NOT AUTHORIZED ****** -SUBSTRING- NON-NUMERIC VALUE SPECIFIED
Operand can have one of the following values: ADD, BRANCH, COMPARE, DELETE, DOWN, EOF, IN, KEY, LEFT, MSG, OPTION, PA, PF, RIGHT, SCRIPT, SEARCH, SET, SUB, or UP. n can specify operand one or operand 2.
Action:
None.
Reason:
CA TPX attempted to open the ACL/E Library pointed to by the ddname ACLLIB. An error occurred and the library is inaccessible. ACL/E scripts are disabled.
Action:
Correct the error and restart CA TPX.
Reason:
An ACL/E program has issued the MSG command. The prefix identifies the application, virtual terminal, and ACL program name. The user text follows in the next line.
Action:
None.
Reason:
The JES file cannot be opened or closed for passthrough printing with the specified virtual printer.
Action:
Contact your JES system programmer.
Reason:
The internal trace table has wrapped around and a new trace entry is overwriting an existing entry that has not been written to the log. This message is issued only when the overflow condition starts.
Action:
None.
Reason:
The overflow condition described in message TPXL0068 has ended. The TRACE component is no longer overwriting entries not yet written to the log. If the condition occurs again, message TPXL0068 is reissued.
Action:
None.
Reason:
A quiesce request has been completed and all sessions have terminated. This message is issued with message TPXL700I.
Action:
None.
Reason:
If the value of cause is PACING COUNT EXCEEDED, the number of recipients processed while sending or saving a message exceeded the pacing count set in the System Options Table (SMRT).
If the value of cause is STORAGE OVERLOAD, the internal storage usage exceeded the overload threshold set in the SMRT.
In either case, the product suspends the processing of the message, allowing the mailbox facility to process other user's tasks. The product resumes processing at the end of the queue of mailbox facility requests after a short delay.
If the cause of this message is an overload and the overload still exists, the processing will be delayed again. When the overload condition is resolved, the product issues message TPXL0072.
Action:
None.
Reason:
The storage overload condition described in message TPXL0071 has been resolved.
Action:
None.
Reason:
An RPL that was passed to VTAM has failed VTAM validity checking. The RPL was rejected by VTAM with a value of X'18'(24) in Register 0. The RPL may have failed VTAM validity checking for the following reasons:
Action:
None.
Reason:
An RPL-based macro request has been issued against an ACB that is not open.
Action:
None.
Reason:
The current screen image has been rejected with a 1005 sense code and is therefore being reset to null.
Action:
None.
Reason:
A terminal or application session generated ten errors in a row. The product will attempt to end the session.
Action:
None.
Reason:
A non-zero return code has been detected and the error management routine has been invoked. In this message, the PLU is usually the real terminal and the SLU is the virtual terminal. The message indicates whether the error occurred on an inbound or outbound activity and whether it was to or from an application or terminal. The REQ field is the RPL request code that is followed by the option bytes from the RPL.
Where applicable, the following information is displayed:
The request codes are documented in IBM documentation on VTAM programming. The return code, feedback, and sense codes are documented in IBM documentation on VSAM messages.
Action:
None.
Reason:
An error was encountered when opening a virtual terminal ACB. This message identifies the following:
The values for Register 15 and the ACB error flag are documented under the OPEN macro in IBM documentation on VTAM programming.
The ACB will be marked as UNAVAIL and will be recovered by the ACB recovery routine. Recovery will not occur if the SMRT INQINT parameter has a value of 0.
Action:
None.
Reason:
An error was encountered when closing a virtual terminal ACB. This message identifies the following:
The values for Register 15 and the ACB error flag are documented under the CLOSE macro in IBM documentation on VTAM programming.
Action:
None.
Reason:
An error was encountered when issuing a VTAM MODCB, TESTCB, or SHOWCB macro. This message identifies the following:
The values for Register 15 and 0 are documented in IBM documentation on VTAM programming.
Action:
None.
Reason:
A receive issued by the product failed because a VTAM buffer pool was exhausted. VTAM signals this by placing RTNCD=8, FDBK2=0 in the RPL of the request. For details, see IBM documentation on VTAM messages.
Action:
None.
Reason:
The specified object had an incorrect record length. The software discovered this while checking VSAM records updated by TPX 3.0 or 2.0 programs that do not have TPX VSAM compatibility installed. Any View facility authorization or CA STX signon information related to the object will not be used because it is unreliable.
This message will appear every time the record is read until the record is written.
Action:
See the Installation Guide for information about setting up VSAM sharing and VSAM compatibility between versions of TPX.
Reason:
This message has many possible wordings.
The TPXL0099 message number is used for diagnostic and debugging messages placed in the code.
Action:
Typically, no action is required. If the same TPXL0099 message appears often and accompanies a specific problem, contact CA Technical Support for assistance.
Reason:
The specified terminal has logged on to CA TPX.
Action:
None.
Reason:
The product is going to build the specified panel in memory.
Action:
None.
Reason:
A terminal logoff was not completed when a logon was received for the same terminal.
Action:
None.
Reason:
The product is going to end the specified session.
Action:
None.
Reason:
The product is going to terminate the specified session because of an error condition.
Action:
None.
Reason:
The specified application is now quiesced. If the command
Q applid was issued, this message appears after the last user in session with this application ends the session. If the command Q applid,SHUT= was issued, this message appears at the time specified.
Action:
None.
Reason:
This message occurs when VTAM returns the application status to the product after an INQUIRE request that indicates the application is not available for session logons or is not defined or found. This may occur when the search limit for inquiry requests is exceeded and the application status is not found. Usually the application is a cross-domain application.
The xxxxxx is the return code and feedback (RCFB) information provided by VTAM; tttttttttttttttttttttttttttt is the meaning of the RCFB.
Action:
Set the ACT table field INQUIRE-ON-APPL-STATUS to NO for this application when the returned status is in error and the application is known to be available. The product will not inquire on this application; it is assumed that application status is available.
Reason:
The specified problem occurred when the product was establishing a PPS session for which the output destination was a JES SYSOUT data set.
Action:
None.
Reason:
These messages may occur if two minutes pass with no activity in a PPS session that has a JES SYSOUT data set as an output destination.
Action:
Correct the specified error and try again.
Reason:
The user has deleted a table in TPXADMIN.
Action:
None.
Reason:
An abend has occurred and the ESTAE routine has been entered to obtain a dump and attempt recovery.
Action:
None.
Reason:
An ACL/E timeout has occurred for the specified program.
Action:
None.
Reason:
A data RU was received while an ACLPGM verb was being processed. The RU is ignored, and execution of the ACL/E program resumes when the called ACL/E gains control.
Action:
None.
Reason:
The product has terminated ACL/E execution because the backward pointer referring from a called ACL/E program to the ACL/E program that called it is no longer valid. This message is sent by the script task after the called ACL/E program has been built.
Action:
None.
Reason:
An ABEND has occurred in a screen manipulation module. Processing will be performed to prevent recurrent ABENDs.
Action:
None.
Reason:
A new LSIB and RUQ have been obtained. The values in the message are for CA Technical Support.
Action:
None.
Reason:
An invalid address pointer has made LSIB recovery impossible. Values in the message are for CA Technical Support.
Action:
None.
Reason:
NSEXIT was driven, but VTAM passed a user correlator that does not point to a valid session block.
Action:
Correct the user correlator and try again.
Reason:
NSEXIT was driven for the specified session before an RPL exit for a VTAM request for that session was completed.
Action:
None.
Reason:
NSEXIT was driven, but VTAM passed a user correlator that does not point to a valid session block.
Action:
Correct the user correlator and try again.
Reason:
A session in PASS mode was requested and the RPL exit for the resulting CLSDST/PASS had not been completed when NSEXIT was driven for the terminal.
Action:
Ignore if this message accompanies TPXL0155.
Reason:
NSEXIT was driven for the specified session before an RPL exit for a VTAM request for that session was completed.
Action:
None.
Reason:
A session in PASS mode was requested and the RPL exit for the resulting CLSDST/PASS had not been completed when NSEXIT was driven for the terminal.
Action:
None.
Reason:
A session in PASS mode was requested and the RPL exit for the resulting CLSDST/PASS encountered a corrupted control block.
Action:
None.
Reason:
The RPL error management routine has been entered for a printer. This message indicates the RPL error and the actions to be taken. See IBM documentation on VTAM messages for information on the return, feedback, and sense codes.
Action:
None.
Reason:
This message indicates that an ACL/E program delete request has failed.
Action:
None.
Reason:
An ACL/E program delete request could not find the ACLPGM.
Action:
None.
Reason:
A VSAM error has occurred. The RTNCD/FDBK values can be found in IBM documentation on VSAM administration.
Action:
None.
Reason:
This message indicates a control block failure.
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
The ADMIN1 file could not be opened.
Action:
See IBM documentation on VSAM administration for information on ACBERFLG values. If ACBERFLG=00, examine the log for prior error messages that may be related to this message.
Reason:
The user administration files could not be opened.
Action:
See IBM documentation on VSAM administration for information on ACBERFLG values. If ACBERFLG=00, examine the log for prior error messages that may be related to this message.
Reason:
The mail file could not be opened.
Action:
See IBM documentation on VSAM administration for information on ACBERFLG values. If ACBERFLG=00, examine the log for prior error messages that may be related to this message.
Reason:
The notepad file could not be opened.
Action:
See IBM documentation on VSAM administration for information on ACBERFLG values. If ACBERFLG=00, examine the log for prior error messages that may be related to this message.
Reason:
This message appears after a DELETE MAILMESSAGE statement is processed. Before the purge began, number user IDs had an aggregate number message locators stored in the MAIL file.
Action:
None.
Reason:
This message appears after a DELETE MAILMESSAGE statement is processed. The variables indicate the number of message locators and messages deleted. Note that messages are deleted only when all message locators for that message are deleted. The use count, which is the number of message locators using the message text, is zero in this case.
Action:
None.
Reason:
This message appears when a bulletin is deleted online or through the Batch facility. The variables have the following meanings:
Indicates the text reference ID.
Indicates the sender of the bulletin. If the bulletin was generated in the Batch facility, the sender will be the job name.
Action:
None.
Reason:
This message appears when a message is deleted online or through the Batch facility. The variables have the following meanings:
Locator reference ID that uniquely identifies the locator. It is the third through eighteenth characters of the text reference ID, except for acknowledgment locators.
Indicates the sender of the message. If the message was generated in the Batch facility, the sender will be the job name.
Indicates the recipient of the message.
Action:
None.
Reason:
This message appears when a message is deleted online or through the Batch facility. The variables have the following meanings:
Indicates the text reference ID.
Indicates the sender of the bulletin. If the bulletin was generated in the Batch facility, the sender will be the job name.
Action:
None.
Reason:
This message appears when a message is deleted online or through the Batch facility. The variables have the following meanings:
Indicates the text reference ID.
Indicates the sender of the message. If the message was generated in the Batch facility, the sender will be the job name.
Indicates the recipient of the message.
Action:
None.
Reason:
The message text record identified by the specified text reference ID was not found when attempting to update the use count. This record was identified in the message locator described by the preceding TPBL0502 or TPXL0502 message.
Action:
Diagnostic message. Normally no action is required. If this message appears often and is accompanied by a problem, call CA Technical Support for further assistance.
Reason:
The names specified in the USERIDS or USERLISTS field could not be found.
Action:
Correct the names and resubmit the job.
Reason:
This message lists the system tables loaded at startup time.
Action:
None.
Reason:
A /P request was printed to the log.
Action:
None.
Reason:
This informational message appears each time the product is started. The variable table-name shows the name of the SMRT specified in the startup procedure. The variable mm/dd/yy hh:mm:ss is the time stamp from the VSAM record. The variable xxxxx038 is the address at which the SMRT is loaded. Note that the VSAM record header is found at xxxxx000. Userid is the user ID who last updated this SMRT.
Action:
None.
Reason:
Modules SSNDPROG and PAVRETY attempt to set the active SEND log using a compare and swap. This message appears if the compare and swap fails. The variables have the following meanings:
Either SSNDPROG or PAVRETY
Address of the rpl currently being sent
Current value of the send log when a compare and swap is performed
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
Modules SNDXPROG and PAVPRG attempt to reset the active SEND log by a compare and save. This message appears if the compare and save fails. The variables have the following meanings:
Either SNDXPROG or PAVPRG
Address of the rpl currently being processed
Current value of the send log when a compare and save is performed
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
This message appears when the active RECEIVE log update fails in ISSUPROG. The variable name identifies the acbname for an SLU receive or the PLU name for a PLU receive.
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
An already queued event is put back in the softcopy queue, but the printer is not currently available. This message is followed by a SNAP of the EB and PSB. The variable printer identifies the printer name.
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
JES was unable to allocate a SYSOUT data set. The variable code identifies the DAIR code.
Action:
Consult with your JES system programmer to correct the JES allocation failure based upon the DAIR code.
Reason:
JES was unable to deallocate a SYSOUT data set. The variable code identifies the DAIR code.
Action:
Consult with your JES system programmer to correct the JES allocation failure based upon the DAIR code.
Reason:
JES was unable to allocate a SYSOUT data set. The variables have the following meanings:
Either VJESPROG or VJESSCNP
DAIR code
Action:
Consult with your JES system programmer to correct the JES allocation failure based upon the DAIR code.
Reason:
JES was unable to de-allocate a SYSOUT data set. The variables have the following meanings:
Either VJESPROG or VJESSCNP
DAIR code
Action:
Consult with your JES system programmer to correct the JES allocation failure based upon the DAIR code.
Reason:
This message appears when you set the "PPS VTAM Idle Session Timeout" field. The variables have the following meanings:
Physical printer name
Virtual printer name
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
This message appears when you set the "PPS JES Idle Session Timeout" field. The variables have the following meanings:
JES printer name
Virtual printer name
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
This message appears when you set the "PPS Release Request Timeout" field. The variables have the following meanings:
Physical printer name
Virtual printer name
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
An abend has occurred and the ESTAE routine has been entered to obtain a dump and attempt recovery.
Action:
None.
Reason:
The product has connected to the file server on the specified CA‑L‑Serv subsystem. This message is informational.
Action:
None.
Reason:
Indicates the prefix of the VSAM file(s) for this CA‑L‑Serv subsystem. This message is informational.
Action:
None.
Reason:
The specified VSAM file has been opened. If indicated, size specifies the size of the I/O buffer for the file. Below-the-line slot pools will use buffer pools of this size. The size was calculated by determining the maximum VSAM record size and rounding that number up to a multiple of 256 bytes. This message is informational.
Action:
None.
Reason:
The specified VSAM file has been closed.
This message may accompany TPXL0704 when the product opens and closes the ADMIN files at start up. The specified files will then be reopened by the TPX administration function. This message is informational.
Action:
None.
Reason:
The specified request made to CA‑L‑Serv has failed. The file DD name is given if the request applies to a specific file (is not a CA‑L‑Serv initialize or terminate request). If applicable, the error fields in the ACB and RPL are formatted and the VSAM key given.
Action:
See the CA-L-Serv portion of the CA Common Services guides and the VSAM guides to determine the correct action based on the codes you receive.
Reason:
The specified VSAM file is processed as a CA Datacom file using the VSAM/Transparency feature in CA Datacom.
Action:
None.
Reason:
The product has determined that the specified VSAM file has either become unavailable or available, and is marking it accordingly.
Action:
If the file is being marked UNAVAILABLE, check the status of CA‑L‑Serv to determine if CA‑L‑Serv is down or why the file has been closed.
Reason:
The product has determined that CA‑L‑Serv is unavailable.
Action:
See the CA‑L‑Serv portion of the CA Common Services guides for information on restoring CA‑L‑Serv.
Reason:
The product is attempting to reconnect to CA‑L‑Serv. This message is informational.
Action:
None.
Reason:
The product's attempt to reconnect to CA‑L‑Serv has either succeeded or failed.
Action:
If the attempt has failed, check the status of CA‑L‑Serv and consult the CA‑L‑Serv portion of the CA Common Services guides.
Reason:
The product was unable to access the specified VSAM file. The file's status is either quiesced or unavailable.
Action:
If the file status is UNAVAILABLE, check the status of CA‑L‑Serv.
Reason:
During CLOSE processing for file ffffffff a DEQ call for this file failed with a return code addressed by R15. R15 addresses a value of xxxxxxYY. YY is DEQ return code failure.
This could prevent a batch RESET INTEGRITY job to fail for file ffffffff.
Action:
Contact TPX support and supply all the logs from the TPX job.
Reason:
This message is used for diagnostic purposes when certain problem conditions exist. You can ignore it if it appears independent of a problem condition.
Action:
None.
Reason:
This message is used for diagnostic purposes when certain problem conditions exist. You can ignore it if it appears independent of a problem condition.
Action:
None.
Reason:
The two possible forms for this message are shown above.
Dialogue between the user and the product cannot continue. The variables have the following meanings:
User ID or NO USER if TERMSB SBUIDX does not point to a UINDEX
Terminal ID
Internal application name (that is, TPXADMIN, TPXVIEW, and so on)
TERMSB or APPLSB address
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
The specified user has tried to sign on or off, but a signon or signoff is already in progress for this user. The variables have the following meanings:
SIGNON or SIGNOFF
User ID or NO USER if TERMSB SBUIDX does not point to a UINDEX
Terminal ID
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
The specified terminal was previously hung when a user signed on or off. This message may appear when a SIGNOFF event is generated by a terminal disconnect or TPXOPER CANCEL command. The variables have the following meanings:
Terminal ID
TERMSB address
Action:
Diagnostic message. Normally no action required. If this message appears often and accompanies a specific problem, contact CA Technical Support for further assistance.
Reason:
These messages appear in the log if there is a failure for a Pass Ticket user attempting to sign on to the product.
Pass ticket generation failed for this userid attempting a signon to an affinity target region or to reconnect after a pass session ends.
Action:
The user should contact the security administrator to determine the reason for the pass ticket generation failure.
Reason:
Pass ticket generation failed for this userid attempting to start an application session through the product using a pass ticket.
Action:
The user should contact the security administrator to determine the reason for the pass ticket generation failure.
Reason:
The above messages appear in the log for a successful generation of a pass ticket for a TPX signon. These are informational messages that only appear if RSVOPT 042 is set to Y (for yes) on panel TEN0096. RSVOPT 042 can be used to verify that pass tickets are being successfully generated for users attempting a signon to an affinity pass TPX region or to reconnect after a pass session ends.
These are informational messages. Pass ticket generation was successful for this userid attempting to signon to an affinity target region or to reconnect after a pass session ends.
Action:
None.
Reason:
The above message appears in the log for a successful session start using a pass ticket. This is an informational message that only appears if RSVOPT 042 is set to Y (for yes) on panel TEN0096. RSVOPT 042 can be used to verify that pass tickets are being successfully generated for session starts.
This in an informational message. Pass ticket generation was successful for this userid attempting to start an application session through the product using a pass ticket.
Action:
None.
Reason:
CA TPX attempted to generate a qualified pass ticket based on CA‑Top Secret or CA‑ACF2 qualified ptktdata profile. Retrieving the information requires the security group to be extracted the from the security system. A failure occurs if the user does not have a group attached to his security record. The variables have the following meanings:
User ID signed on
Session selected
Action:
Have the security administrator add a group to the CA‑Top Secret or CA‑ACF2 security record of the user.
Reason:
CA TPX attempted to generate a qualified pass ticket based on CA‑Top Secret or CA‑ACF2 pktdata profiles. The appropriate ptktdata profile does not exist in the security database. The session request fails.
Action:
Have the security administrator define qualified PTKTDATA profiles in the CA‑Top Secret or CA‑ACF2 security database.
Reason:
Pass ticket or qualified pass ticket use is not permitted with a different userid than the userid used to sign on to the product under which the session request is being made. The authorization is impossible to verify. Session setup fails. The variables have the following meanings:
User ID signed on
Session selected
Acluser specified in the user, profile, or ACT definition of the application
Action:
Either set the Passticket or Qualified Passticket to No or remove the acluser in the session definition.
Reason:
CA TPX requires either CA‑Top Secret or CA‑ACF2 as the external security system under which it runs to generate qualified pass tickets. It is determined that neither of the above is currently active. Generate Qualified Passticket is set to Y and Generate Passticket is set to N, which limits pass tickets to the qualified type. The session request fails because a qualified pass ticket cannot be generated and a pass ticket is not permitted.
Action:
Set Generate Passticket to Y.
Reason:
CA TPX attempted to generate a qualified pass ticket based on CA‑Top Secret or CA‑ACF2 qualified ptktdata profiles. Retrieving the information requires the Group to be extracted from the security system. A failure occurs if the user does not have a Group attached to his security record.
Action:
Have the security administrator add a Group to the CA‑Top Secret or CA‑ACF2 security record of the user.
Reason:
CA TPX attempted to generate a qualified pass ticket based on CA‑Top Secret or CA‑ACF2 qualified ptktdata profiles, but no such profile exists in the security database. The session request fails.
Action:
Have the security administrator define qualified profiles to the CA‑Top Secret or CA‑ACF2 database.
Reason:
When a pass ticket is required based only on qualified profiles, CA‑Top Secret or CA‑ACF2 must run on the system that CA TPX is running on. The session request fails.
Action:
Either set Generate Qualified Passticket to N or set Generate Passticket to Y in the user record or in the user profile record.
Reason:
This is a general informational message.
If the informational-message is a VSAM INTEGRITY message, a serious error may have occurred in VSAM sharing. A U999 abend occurs, and one of the following informational-messages may be issued:
The product cannot access the VSAM files for one of the following reasons:
You did not set the VSAM sharing options correctly. If the first VSAM share option is less than three, no VSI is built.
VSAM or z/OS problems may exist.
VSAM sharing is not implemented for TPX/VM.
VSAM sharing requires the product to be authorized.
Two copies of the product (most likely running in batch) are executing at the same time. This results in too much contention for the VSAM files and is not recommended.
A first time user has selected VSAM sharing on a VSAM file. Your VSAM files may have been moved, which requires deleting control record 0.
Control record 0 is written to the VSAM file if one is not found. See the CONTROL RECORD 0 NOT FOUND message above.
Your VSAM files have been moved. Control record 0 is deleted because the information it contains is inaccurate.
A cross-system change to the VSAM files has been detected. The product updates the VSAM shared information (VSI) for the system that is out of sync.
The product has expanded one of the VSAM files. The product will pass information about the change to other copies of TPX by rewriting control record 0, which will contain information about the change.
The product has encountered an error in reading or writing control record 0. The VSAM file might be corrupted. Locate a backup of the VSAM file. If you cannot delete control record 0 with TPX batch administration, restore the VSAM file from the backup and then delete control record 0 using batch administration
The product has determined that one of the VSAM files has been moved. The product will delete control record 0. If the VSAM file was moved within the same pack, the product cannot detect that it has been moved and will not delete control record 0.
Action:
If the message text indicates that a VSAM problem exists, fix the problem as described above.
Reason:
This message displays the text of statements in your batch job as the statement is executed.
Action:
None.
Reason:
This message appears at the start of your batch job. It indicates the name of your job and where it is running.
Action:
None.
Reason:
This message appears at the start of your batch job. It indicates your user ID on VM.
Action:
None.
Reason:
The MSGFILE DD statement required in the CONVERT MSGFILE or CONVERT MAIL statement is missing.
Action:
Add the MSGFILE DD statement to the CONVERT MSGFILE or CONVERT MAIL statement.
Reason:
Your SYSIN file is not defined.
Action:
Define your SYSIN file and try again.
Reason:
The specified data definition name is not defined. The data definition name was specified in a USING or GIVING parameter immediately preceding the message.
Action:
Define the data definition name and try again.
Reason:
An operator command (indicated by command text), was issued by userid.
Action:
None.
Reason:
The product was unable to open the specified file. The data definition name was specified in a USING or GIVING parameter immediately preceding the message.
Action:
Check that the data definition name is defined correctly and referring to the correct file.
Reason:
The product was unable to open the SYSIN file.
Action:
Check that the SYSIN file is defined correctly and referring to the correct file.
Reason:
The data contained in the specified record was too long for the file where the product was writing it. The software has truncated the data in the record to fit the file. The file containing the truncated record is the file specified in the most recent GIVING parameter.
Action:
Redefine your space allocation appropriately and try again.
Reason:
The product encountered an internal error in trying to write to the specified record. The file where the software attempted to write the record is the file specified in the most recent GIVING parameter.
Action:
Contact CA Technical Support.
Reason:
The product was unable to read the specified file because the file was never written.
Action:
Check that the file was extracted before being specified as a USING parameter.
Reason:
The product was unable to close the specified file. The data definition name was specified in a USING or GIVING parameter immediately preceding the message.
Action:
Check your definition for the file.
Reason:
The product was unable to close the SYSIN file.
Action:
Check your SYSIN definition.
Reason:
The product has read the specified number of records from the specified file.
Action:
None.
Reason:
The product has read the specified number of records from the SYSIN file.
Action:
None.
Reason:
The product has written the specified number of records into the specified file.
Action:
None.
Reason:
A component (usually VSAM) has returned the specified return code. This message relates to the statement echoed in the most recent TPBL1000 or TPXL1000 message.
This message is usually found with other, indented, messages that elaborate on the problem. If a VSAM error has occurred, the VSAM record key, or the first record of the table is indicated in such a message.
Possible values of component and the component's corresponding action are described in the following table.
Action:
Refer to the accompanying messages for help in determining the problem.
|
Component |
Action |
|---|---|
|
VSAM GET |
Performs VSAM input of a single record. |
|
VSAM PUT |
Performs VSAM output. |
|
VSAM ERA |
Performs VSAM erasure of a record or table. |
|
VSAM GSQ |
Performs VSAM input of the names of all tables of a given type. |
|
VSAM GSP |
Performs VSAM input of a table primary record(s). |
|
VSAM GSS |
Performs VSAM input of a table secondary record(s). |
|
VGET |
References the value of a variable. The optional-info specifies the variable. |
|
VPUT |
Sets the value of a variable. The optional-info specifies the variable. |
|
UIDXVGET |
References the value of a variable. A UIDX record was being processed by EXTRACT when the message was issued. The optional-info specifies the variable. |
|
PIDXVGET |
References the value of a variable. A PIDX record was being processed by EXTRACT when the message was issued. The optional-info specifies the variable. |
|
UENTVGET |
References the value of a variable. A UENT record was being processed by EXTRACT when the message was issued. The optional-info specifies the variable. |
|
PENTVGET |
References the value of a variable. A PENT record was being processed by EXTRACT when the message was issued. The optional-info specifies the variable. |
|
MRG CP8 |
Assists in building a merged user. |
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message included a command that the product does not recognize.
Action:
Check that:
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message did not include a required parameter list in a command.
Action:
Insert the parameter list and try again.
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message contained an error in the syntax of a parameter list.
Action:
Correct the syntax and try again.
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message included a parameter that the product does not recognize.
Action:
Replace the parameter with one that is valid and try again.
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message specified a parameter that is too small.
Action:
Replace the parameter with one that is larger and try again.
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message specified a parameter that is too large.
Action:
Replace the parameter with one of fewer characters and try again.
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message requires a preceding statement.
Action:
Add the required statement and try again.
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message requires a preceding entry.
Action:
Add the required entry and try again.
Reason:
The product encountered an end-of-file while parsing a statement.
Action:
Check the syntax in the SYSIN file.
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message requires a missing parameter.
Action:
Add the required parameter and try again.
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message includes a parameter that has an invalid value.
Action:
Replace the parameter with one that is valid and try again.
Reason:
The last control statement echoed in a TPBL1000 or TPXL1000 message is missing a parenthesis at the end of a parameter list.
Action:
Add the parenthesis and try again.
Reason:
You did not specify any criteria in an EXTRACT statement, so the product did not extract any records.
Action:
Enter the EXTRACT statement with extraction criteria and try again.
Reason:
This message is produced with another, preceding message to indicate that the product was adding the specified record when the accompanying message was sent.
Action:
None.
Reason:
This message is produced with another, preceding message to indicate that the product was copying the specified record when the accompanying message was sent.
Action:
None.
Reason:
This message is produced with another, preceding message to indicate that the product was copying the specified sessions when the accompanying message was sent.
Action:
None.
Reason:
This message is produced with another, preceding message to indicate that the product was deleting the specified record when the accompanying message was sent.
Action:
None.
Reason:
This message is produced with another, preceding message to indicate that the product was updating the specified record when the accompanying message was sent.
Action:
None.
Reason:
This message is produced with another, preceding message to indicate that the product was evaluating the specified record when the accompanying message was sent.
Action:
None.
Reason:
An ADD statement failed because the record to be added already existed in the ADMIN file.
Action:
Delete the existing record and use the ADD statement.
Reason:
An ADD statement attempted to add a session to a user or profile that does not exist.
Action:
Add the user or profile before adding a session to the user or profile.
Reason:
The specified record was successfully added.
Action:
None.
Reason:
The specified record was successfully deleted.
Action:
None.
Reason:
The specified request was against an existing record and all processing is complete. Review the prior messages for the results of the request.
Action:
None.
Reason:
The specified request could not be completed. The partially built record has been purged.
Action:
None.
Reason:
The specified record was successfully updated.
Action:
None.
Reason:
One of the fields (indicated by field-name in the message) you specified to be updated is a primary variable. The primary variables, UIDXNAME, PIDXNAME, UENTUSER, and PENTUSER cannot be changed with the UPDATE command.
Action:
To update a field that is a primary variable, you must delete the existing record and then add a new record that has the new value for the field.
Reason:
The product has found session records for the specified user or profile but no corresponding user or profile record exists.
Action:
Add a user or profile record or delete the records.
Reason:
The fields you specified to be updated are primary variables which cannot be changed. The product did not perform the update. The primary variables, UIDXNAME, PIDXNAME, UENTUSER, and PENTUSER cannot be changed with the UPDATE command.
Action:
To change the primary variables delete the existing record and then add a record that has new values for the fields.
Reason:
The product did not find the specified field when trying to update a record.
Action:
None.
Reason:
The product did not update any fields in the specified record while executing an UPDATE command.
If preceded by the message L1010 VSAM GET RETURN CODE IS 12, the table containing the specified record was locked by another user who was updating the table.
Action:
None.
Reason:
The specified record was not added because a record of the same name already exists. This message can occur after an ADD USERPROF or ADD USERMAGN statement.
Action:
None.
Reason:
The specified record was not found so it could not be deleted. This message can occur after a DELETE USERPROF or DELETE USERMAGN statement.
Action:
None.
Reason:
You specified an invalid object type for this command.
Action:
Specify a valid object type and try again.
Reason:
You did not specify any field names in the line definition of a REPORT statement.
Action:
Add line definitions to the REPORT statement and try again.
Reason:
The product has encountered undefined profiles while executing an EXTRACT command and cannot build the specified user.
Action:
Either define or delete the profiles.
Reason:
The batch facility was unable to delete a session because the session type (CA TPX or CA‑STX) did not match that specified in the DELETE statement.
Action:
Check the session type and try again.
Reason:
The batch facility was unable to add a session to a profile or user because, although the profile or user exists, the signon authority of the profile or user (CA TPX or CA‑STX) did not match that of the session. For example, you tried to add a CA TPX session to a profile that only has a CA‑STX component.
Note that you cannot assign CA TPX or CA‑STX signon authority to a user by assigning the user a profile with that authority.
Action:
Check the session type and try again.
Reason:
The batch facility was unable to copy a session because, although the session exists, the session type (CA TPX or CA‑STX) does not match that specified in the COPY statement.
Action:
Check the session type and try again.
Reason:
The batch facility was unable to copy, add, or delete a session because you are authorized for both CA TPX and CA‑STX but did not specify which type of session you want to add. Specify TPX or STX in the ADD, COPY, or DELETE command.
Action:
Check the session type and try again.
Reason:
The batch facility was unable to delete a profile or user because, although the profile or user exists, the type of user or profile (CA TPX or CA‑STX) does not match that specified in the command. For example, you might have specified DELETE STX USER USR05 when USR05 is a CA TPX user.
Action:
Check the user or profile type and try again.
Reason:
The batch facility was unable to update a profile or user because, although the profile or user exists, the profile or user is not authorized for the specified component. For example, you may have executed a UPDATE STX USER statement but the user does not have a CA‑STX segment.
Action:
Check the profile or user type and try again.
Reason:
The batch facility was unable to copy a profile or user because, although the profile or user exists, the profile or user is not authorized for the specified component. For example, you may have executed a COPY??TX USER statement but the user does not have a CA‑STX segment.
Action:
Check the profile or user type and try again.
Reason:
A DELETE USERSESSION statement is being processed. The record to be deleted does not explicitly exist in the user definition. It may exist in a profile. A user session override record is being created to indicate that the record is deleted.
Action:
None.
Reason:
While building the user definition for the specified record a logic error occurred. If b is N, there is an obsolete session override record on file that will be deleted the next time the user signs on. If b is Y, this message is followed by a U918 user abend.
Action:
None.
Reason:
The product was unable to initialize VSAM integrity for the specified file because the file was found unopen. This message appears after a TPBL0420, TPBL0421, or TPBL0423 message.
Action:
Check that the data definition name is defined and try again.
Reason:
You used a masking character, specified by maskchar, in an invalid location. Your batch programs continues, depending on the value of the variable MASKERLV:
Action:
Check and correct your usage of masking characters.
Reason:
You used a masking character, specified by maskchar, in an invalid location and the variable MASKERLV=1. The product does not process the item containing the invalid masking character and moves on to the next item.
Action:
Check and correct your usage of masking characters.
Reason:
The record was not on file. This message accompanies the TPBL1010 message.
Action:
Make sure you are using the correct record name.
Reason:
The product could not access the table because it was held by another address space. This message accompanies the TPBL1010 message.
Action:
Make sure you are using the correct table.
Reason:
You specified an incorrect variable. This message accompanies the TPBL1010 message. If this message occurs during extraction of profile records, a selection field is undefined. If this message occurs during an update, you may be updating a read-only variable.
Action:
Correct the variable and try again.
Reason:
You specified an incorrect value for a variable. This message accompanies the TPBL1010 message.
Action:
Correct the value and try again.
Reason:
You specified a variable that does not have a value assigned to it. If the variable is displayed on a panel, it appears as underscores. This message accompanies the TPBL1010 message and applies only to profile variables.
Action:
Correct the variable assignment if necessary.
Reason:
The product has successfully performed some task such as initializing VSAM integrity.
Action:
None.
Reason:
You specified an incorrect profile. This message accompanies the TPBL1010 message.
Action:
Correct the profile and try again.
Reason:
An ADD USERMAGN statement specified a user that does not have user administration authority, and the control statement did not indicate what user authority to confer, CA TPX or CA‑STX. The authority will be determined by the LMP key.
Action:
None.
Reason:
The USING parameter of the CONVERT statement contained too many ddnames. When converting a STXT, STX users or STX profiles, one ddname is required in the USING parameter. When converting an NPT, two ddnames are required.
This message appears once for each excessive ddname.
Action:
Specify the correct number of ddnames in the USING parameter and try again.
Reason:
The USING parameter of the CONVERT statement did not specify the required number of ddnames. The Batch facility will stop executing the CONVERT statement.
When converting a STXT, STX users or STX profiles, one ddname is required in the USING parameter. When converting an NPT, two ddnames are required.
Action:
Specify the correct number of ddnames in the USING parameter and try again.
Reason:
The batch facility was unable to delete the user session because the user does not have the specified session.
Action:
Check the user's sessions and try again.
Reason:
This message appears after an ADD MAGN statement was executed to indicate that CA‑STX authority was assigned to the user specified in the statement.
Action:
None.
Reason:
This message appears after an ADD MAGN statement was executed to indicate that authority was assigned to the user specified in the statement.
Action:
None.
Reason:
This message appears after a COPY USERSESSION statement is executed. The session that was copied exists as an override to a session in a profile.
If a session of this name exists in a profile assigned to the target user, the override will have effect; but the override fields cannot be verified as being appropriate for the overridden session.
If a session of this name does not exist in a profile assigned to the target user, the override record will be written to the file, however, the session will:
Action:
None.
Reason:
You have tried to add or convert a CA‑STX user that is already recorded as a TPX saved dynamic user. The ADD or CONVERT statement would make the user static, but "Optional Parameter 25" in the System Options Table (SMRT) is on, which disallows such a change.
Action:
If you want to add or convert the user as a static user, you must set "Optional Parameter 25" off for the remainder of the batch run and then add the user. You can do this by placing a statement SET SOTOP065 'N' in the batch control stream before the ADD or CONVERT statement.
If you want the user to remain dynamic, and be able to sign on to CA‑STX, you must configure this product to allow dynamic users.
Reason:
You are converting or adding a CA TPX user that is already recorded as a TPX saved dynamic user. The CONVERT or ADD statement makes the user static. "Optional Parameter 25" in the System Options Table (SMRT) is off, so CA TPX allows the user to become static.
Action:
None
TPX OPERATOR SESSION ABORTED, TO PREVENT POSSIBLE LOOP SCENARIO
Reason:
TPX has discovered a possible loop situation in the TPX operator code.
The session is cancelled. A related TPX00003 SVC dump may be taken.
Action:
Save the SVC dump and all output from the TPX job. Contact TPX support.
Delete of the default profile is not allowed
Reason:
A user has attempted to delete the default profile in a TPX batch utility job.
TPX will not let a user delete the default profile on a system using dynamic profiles.
Action:
None.
Reason:
You have invoked the parse table trace. The product is using the specified parse table.
Action:
None.
Reason:
The specified user or profile was successfully built when the product executed an EXTRACT statement.
Action:
None.
Reason:
A profile or user entry with the specified session ID has not been extracted because it does not match the extraction criteria you specified in the EXTRACT statement.
Action:
None.
Reason:
The specified user or profile has not been extracted because it does not match the extraction criteria you specified in the EXTRACT statement.
Action:
None.
Reason:
The product is about to build the specified user or profile while executing an EXTRACT statement.
Action:
None.
Reason:
The product is checking for records that include the specified field, which you specified as extraction criteria in an EXTRACT statement. In this case the extraction criteria is a primary variable.
Action:
None.
Reason:
The product is checking for records that include the specified field, which you specified as extraction criteria in an EXTRACT statement.
Action:
None.
Reason:
The product is currently reading the specified record.
Action:
None.
Reason:
The product is currently writing the specified record.
Action:
None.
Reason:
The product is about to add the specified record.
Action:
None.
Reason:
The product is about to copy the specified record.
Action:
None.
Reason:
The product is about to delete the specified record.
Action:
None.
Reason:
The product is about to update the specified record.
Action:
None.
Reason:
While creating a report, the product has read an extract record identified by the specified variable management SYMCB code.
Action:
None.
Reason:
You specified blank spaces in the field name specified in an EXTRACT statement. This is invalid. Blank spaces will consist of a b for every blank space. For example, the following message would indicate that the field included three blank spaces:
TPBL1099 bbb REJECTED
Action:
Specify the field name without blank spaces and try again.
Reason:
This message shows VTAM APPL statements generated as a result of the current active model and the current VTAM modeling statement.
Action:
None.
Reason:
The parameters on the TPX,MDL statement must be in sets of four parameters (start value, type, count and order). If there is only one set of parameters, the order parameter can be skipped.
Action:
Correct the statement and re-run the job.
Reason:
The start value parameter cannot be more than seven characters in length.
Action:
Correct the statement and re-run the job.
Reason:
There is an invalid character in one of the start value parameters. Valid characters are based upon the type parameter as follows:
Action:
Correct the statement and re-run the job.
Reason:
A character in the start value parameter is valid but not for the type parameter. Valid characters for each type parameter are as follows:
Action:
Correct the statement and re-run the job.
Reason:
The type parameter cannot be more than one character in length.
Action:
Correct the statement and re-run the job.
Reason:
The type parameter must be one of the following:
Action:
Correct the statement and re-run the job.
Reason:
The count parameter cannot be more than four characters in length.
Action:
Correct the statement and re-run the job.
Reason:
The count parameter must be greater than 0 and less than 10000.
Action:
Correct the statement and re-run the job.
Reason:
The count parameter would cause all characters of the start value parameter to overflow.
Action:
Correct the statement and re-run the job.
Reason:
The order parameter cannot be more than one character in length.
Action:
Correct the statement and re-run the job.
Reason:
The order parameter must be greater than 0 and less than 8.
Action:
Correct the statement and re-run the job.
Reason:
Each order parameter on a statement must contain a unique value from 1 through 7.
Action:
Correct the statement and re-run the job.
Reason:
The order parameters specified on a statement should not contain any missing values.
Action:
Correct the statement and re-run the job.
Reason:
The parameter list on a TPX,MDL statement must not extend beyond column 71.
Action:
Correct the statement and re-run the job.
Reason:
The specified field (either LUNAME or ACBNAME) must not be greater than eight characters in length.
Action:
Correct the statement and re-run the job.
Reason:
The specified field (either LUNAME or ACBNAME) that gets generated based upon the model parameters, must not be greater than eight characters in length.
Action:
Correct the statement and re-run the job.
Reason:
Either the LUNAME, for an APPL statement, did not contain any wildcard characters or the attempt to generate an LUNAME, based upon the model parameters, resulted in an error.
Action:
Correct the statement and re-run the job.
Reason:
A format error was encountered in the APPL statement being processed.
Action:
Correct the statement and re-run the job.
Reason:
The combination of model parameter sets resulted in more than 9999 APPL statements being generated.
Action:
The generation of the APPL statements for this model statement is stopped after the 9999th one. If more are desired, create additional APPL models for the additional values.
Reason:
Some unexpected error was encountered.
Action:
Re-run the job. If this continues, contact CA Technical Support.
Reason:
VTAM APPL statements will be generated based upon the current active model and the current VTAM modeling statement.
Action:
None.
Reason:
TPX batch was unable to open the file containing the STXT to be converted.
Action:
Check that the data definition name is defined correctly and referring to the correct file.
Reason:
The source code of the STXT being converted exceeded the buffer. TPX batch was unable to convert the STXT.
Action:
Check the STXT source code to determine why it used so much space.
Reason:
The batch facility is beginning to convert STXT source definitions.
Action:
None.
Reason:
The STXT being converted contained parsing errors in the definitions. This message will be accompanied by one or more of the parse error messages, which have the TPXL or TPBL prefix and numbered 1213-1245. These messages will specify the error and, if possible, give options for correcting the error.
Action:
Refer to accompanying messages and make corrections as necessary to the STXT.
Reason:
The batch facility has finished converting STXT source definitions.
Action:
None.
Reason:
The batch facility was unable to perform a GETMAIN.
Action:
Check your region size and space allocations.
Reason:
The STXT being converted contained an invalid ACIPATH parameter. The specified default is being used.
Action:
Change the parameter value if you do not want to use the specified default.
Reason:
The STXT being converted contained TOGGLE and BREAK parameters that were set to the same value. This is invalid. The specified defaults are being used.
Action:
Change the parameter values if you do not want to use the defaults.
Reason:
The STXT being converted contained an invalid value for the CALLPSZ parameter. The specified default is being used.
Action:
Change the parameter value to one of the valid values if you do not want to use the default.
Reason:
The STXT being converted contained an invalid value for the SPOLDST parameter. The specified default is being used.
Action:
Change the value of the SPOLDST parameter to one of the valid options if you do not want to use the default.
Reason:
The below-the-line CA‑STX slot pool assignments do not add up to 100%.
Action:
Correct the slot pool assignments.
Reason:
The above-the-line CA‑STX slot pool assignments do not add up to 100%.
Action:
Correct the slot pool assignments.
Reason:
The batch facility is starting to convert NPT records.
Action:
None.
Reason:
The batch facility has finished converting NPT records.
Action:
None.
Reason:
The source code of the APPL or table being converted exceeded the buffer. The Batch facility was unable to convert the definition.
Action:
Check the source code to determine why it used so much space.
Reason:
The source statement being converted did not contain a valid command.
Action:
Specify one of the valid commands and try again.
Reason:
The NPT being converted contained parsing errors in the definitions. This message will be accompanied by one or more of the parse error messages, which have the TPXL or TPBL prefix and numbered 1213-1245. These messages will specify the error and, if possible, give options for correcting the error.
Action:
Refer to accompanying messages and make corrections as necessary to the NPT.
Reason:
An XIDGEN command contained a label consisting of too many characters. The definition will not be converted.
Action:
Correct the label and try again.
Reason:
An XIDGEN command was missing a statement label.
Action:
Add the label and try again.
Reason:
The source code of the APPL definition being converted exceeded the buffer. The Batch facility was unable to convert the definition.
Action:
Check the source code to determine why it used so much space.
Reason:
A source statement did not contain a valid application ID.
Action:
Check and correct the application ID and try again.
Reason:
The source statement contained an application ID that is already being used.
Action:
Check and correct the application ID and try again.
Reason:
A source statement contained an LUSUFX parameter that included low/high limits that were of unequal length. The limits must consist of one to seven characters and be of equal length.
Action:
Check and correct the suffix values and try again.
Reason:
A source statement specified switched LU names that were longer than eight characters.
Action:
Specify LU prefix and suffix parameters that will create names of eight characters or less and try again.
Reason:
A source statement contained an LUSUFX parameter that specified an upper limit that was lower than the specified lower limit.
Action:
Change the value of the upper limit if you do not want it set equal to the lower limit.
Reason:
A source statement contained a COLS parameter with an invalid value. The specified default value was assigned.
Action:
Change the parameter value if you do not want to use the default.
Reason:
A source statement contained a COL1 parameter that has a value greater than that given in the COLS parameter.
Action:
Specify a value for COL1 that is equal or less than the value specified in the COLS parameter.
Reason:
A source statement specified ASCII/EBCDIC translation or set ASCII parity or both for a 3270 application. This is not valid. The TRAN parameter was set to NO.
Action:
None.
Reason:
ASCII/EBCDIC translation was not specified but parity was. This is not valid. Parity is ignored.
Action:
None.
Reason:
A source statement specified that the DBCS parameter be set to K and that the KATAKAN parameter be set to NO. This indicates that the application supports double-byte characters for Katakana, but the Katakana is not specified.
Action:
Specify the correct values for the doublebyte-character option and Katakana.
Reason:
A source statement specified that the DBCS parameter be set to OFF or A and that the KATAKAN parameter be set to YES. This indicates that the application does not support double-byte characters for Katakana, but Katakana is specified.
Action:
Specify DBCS=K if the application supports Katakana.
Reason:
A source statement included a Kanji or Katakana shift code that consists of an invalid number of digits.
Action:
Specify a code consisting of 2, 4, or 6 hex characters.
Reason:
A source statement included an end-of-line sequence for XMODEM that consists of an invalid number of characters.
Action:
Specify a sequence consisting of 2 or 4 hex characters.
Reason:
A source statement specified an invalid CALLADDR parameter.
Action:
Specify an address consisting of 1 to 15 hex characters and try again.
Reason:
A source statement specified an invalid maximum packet size in the CALLPSZ parameter.
Action:
Specify a valid maximum packet size of 16, 32. 64. 128. 256, 512, 1024, 2048, or 4096.
Reason:
The source statement contained an invalid MCHADDR parameter.
Action:
Specify an address consisting of 1 to 15 hex characters and try again.
Reason:
A source statement specified an invalid DNIC parameter. The data network ID code (DNIC) does not match the first four digits of the MCHADDR parameter. The DNIC parameter will be ignored and the first four digits of the specified MCHADDR will be used.
Action:
Change the DNIC value if you do not want the first four digits of the MCHADDR used.
Reason:
A source statement specified a DNIC parameter that does not contain four digits.
Action:
Specify a valid DNIC and try again.
Reason:
A source statement specified an OUF parameter that does not contain an even number of digits.
Action:
Specify a valid OUF value and try again.
Reason:
A source statement specified an odd number of values for the national PAD parameters. An even number of values, consisting of the parm-number and value for each parameter, must be specified.
Action:
Specify valid values and try again.
Reason:
A source statement specified HP2622 function-key-display options but the specified terminal emulation type is not HP2622. The function-key-display options will be ignored.
Action:
None.
Reason:
A source statement specified either PAD=INTEGRATED or MCH for a 3270 application. PAD must be either transparent or set to GATE.
Action:
Correct the PAD value and try again.
Reason:
An invalid byte was found in the translate table being converted.
Action:
Check and correct the translate table and try again.
Reason:
An invalid line was found in the translate table being converted.
Action:
Check and correct the translate table and try again.
Reason:
A source statement specified a translate table that could not be found.
Action:
Check the source statement and specify a valid translate table.
Reason:
A source statement is missing required parameters.
Action:
Check the source statement and specify either IDBLK and IDNUM or STAID.
Reason:
A source statement specified IDBLK or IDNUM without the other. Both must be specified together.
Action:
Check the source statement and specify both IDBLK and IDNUM.
Reason:
A source statement specified IDBLK and IDNUM with STAID. These parameters cannot be specified together.
Action:
Check the source statement and specify either IDBLK and IDNUM, or STAID.
Reason:
A source statement specified a count value without a base value.
Action:
Check the source statement and specify a base value.
Reason:
A source statement did not specify a base or a count value.
Action:
Check the source statement and specify base and count values.
Reason:
A source statement specified an increment without a count value.
Action:
Check the source statement and specify a count value.
Reason:
The source statement specified an invalid value for the IDBLK parameter.
Action:
Specify a IDBLK value consisting of three hexadecimal digits.
Reason:
A source statement specified an invalid value for the IDNUM parameter.
Action:
Specify an IDNUM value consisting of five hexadecimal digits.
Reason:
A source statement specified an invalid value for the STAID parameter.
Action:
Specify a STAID value consisting of five hexadecimal digits.
Reason:
A source statement specified an invalid IDNUM parameter. The base, count, and increment values will produce IDNUM values larger than the maximum possible 5-digit hexadecimal number.
Action:
Specify a valid value for the IDNUM parameter.
Reason:
A source statement contained an invalid STAID parameter The base, count, and increment values will produce station IDs larger than the maximum possible 8-digit hexadecimal number.
Action:
Specify a valid value for the STAID parameter.
Reason:
A source statement specified a station ID table that is too large. The count of entries is maintained in a signed halfword integer field. An attempt to build a table with more than 32,767 entries will produce this message.
Action:
Check the station ID table and remove some entries.
Reason:
A source statement specified an empty password prompt table.
Action:
Check the table if necessary.
Reason:
A source statement specified a PSWGEN command without specifying a label.
Action:
Correct the source statement and try again.
Reason:
A specified alias refers to a duplicate application ID.
Action:
Correct the alias and try again.
Reason:
The specified GATE application refers to a specified MCH table that does not exist.
Action:
Check the MCH definition and try again.
Reason:
The specified 3270 application refers to a specified station ID table that does not exist.
Action:
Check the station ID table reference and try again.
Reason:
The specified application refers to the specified password table which does not exist.
Action:
Check the password table reference and try again.
Reason:
The specified parameter must be included in the source statement when the PAD option is set as specified.
Action:
Add the parameter and try again.
Reason:
The specified NPT parameter does not apply when the PAD option is set as specified.
Action:
None.
Reason:
The specified NPT parameter is required when the TERM option is set as specified.
Action:
Add the required parameter and try again.
Reason:
The specified NPT parameter does not apply when Terminal Emulation is set as specified.
Action:
None.
Reason:
The batch facility was unable to open the NPT source definitions.
Action:
Check the data definition name for the NPT data set.
Reason:
The CONVERT statement for the NPT must include a ddname that specifies the data set or data set member that contains the translate tables used by the NPT.
Action:
Correct the CONVERT statement and try again.
Reason:
The CONVERT MSGFILE or CONVERT MAIL statement requires the MSGFILE DD statement to reference a valid message file from a prior release of TPX. The file has been successfully opened, but the first record is not the INFO header record. This file is either initialized or damaged.
Action:
Specify a valid message file.
Reason:
The list name you specified to convert already exists on the MAIL VSAM file and the contents of the lists are the same (contain the same entries in the same order). If you specified REPLACING, the list is not replaced to preserve the TITLE and last update information.
Action:
None.
Reason:
The list name you specified to convert does not exist on the MSGFILE. It already has been converted.
Action:
None.
Reason:
The list name you specified to convert already exists on the MSGFILE. Because you specified for it to be replaced, the list was converted.
Action:
None.
Reason:
The list name you specified to convert already exists on the MSGFILE. You did not specify for it to be replaced.
Action:
None.
Reason:
The list you specified to convert contains something other than user IDs. MSGFILE can only hold lists of user IDs.
Action:
Specify a list containing only user IDs.
Reason:
The MSGFILE is full, so no more records can be converted.
Action:
Take one of the following actions:
Reason:
This message appears after a CONVERT MAIL statement is processed. A VSAM error occurred reading messages from the VSAM MAIL file. The message text entered in the log corresponds to the online message with the number MENGnnnn. The message appears in the language specified in the SMRT. It is informational only.
Action:
None.
Reason:
The specified user is using the View facility viewing another user's session, as specified.
Action:
None.
Reason:
The specified user is using the View facility to track another user as specified.
Action:
None.
Reason:
The specified user is no longer using the View facility to view another user's session, as specified.
Action:
None.
Reason:
The specified user is no longer using the View facility to track another user as specified.
Action:
None.
Reason:
The specified user has started a Conference feature conference session. The session is on the specified session.
Action:
None.
Reason:
The specified user has joined a Conference feature conference session. The conference was started by the specified user on the specified session.
Action:
None.
Reason:
The specified user is no longer using the Conference feature to join a conference started by the specified user on the specified session.
Action:
None.
Reason:
The specified user has ended the Conference feature conference session. The conference was on the specified session.
Action:
None.
Reason:
The specified user is using the Record/Playback feature to record the specified session.
Action:
None.
Reason:
The specified user is no longer using the Record/Playback feature to record the specified session.
Action:
None.
Reason:
The specified user is using the Record/Playback feature to playback a recorded session from the Playback library.
Action:
None.
Reason:
The specified user is no longer using the Record/Playback feature to playback a recorded session from the Playback library.
Action:
None.
Reason:
The specified user has started a Trainer feature training session. The session is on the specified session.
Action:
None.
Reason:
The specified user has joined Trainer feature training session. The training session was started by the specified user on the specified session.
Action:
None.
Reason:
The specified user has ended a Trainer feature training session. The training session was on the specified session.
Action:
None.
Reason:
The specified user is using the Session Assist feature with the specified user and session.
Action:
None.
Reason:
The specified user is no longer using the Session Assist feature with the specified user and session.
Action:
None.
Reason:
The specified user is using Playback Library Maintenance to unload the specified data set.
Action:
None.
Reason:
The specified user is using Playback Library Maintenance to load the specified data set.
Action:
None.
VIEW SECURITY CHECK ERROR FOR: userid REASON:reason
Reason:
The attempt to read the VSAM user record for the viewer/assister failed with the reason stated. The userid is the viewer's user ID. The reason can be either RECORD NOT FOUND or RECORD IN USE.
Action:
None.
Reason:
The specified user set the started Conference as private and selected the specified user as a valid participant. The session is on the specified session.
Action:
None.
Reason:
The specified user deleted the Playback session identified by the specified user and description.
Action:
None.
Reason:
The specified user modified the characteristics of the Playback session identified by the specified user and description.
Action:
None.
Reason:
The specified user left a training session. The training session was started by the specified user on the specified session.
Action:
None.
Reason:
The specified user registered for a training session. The training session was set up by the specified user on the specified session.
Action:
None.
Reason:
The specified user registered the second specified user for a training session. The training session was set up by the specified user on the specified session.
Action:
None
Reason:
The specified user scheduled a training session. The training session was set up by the specified user on the specified session.
Action:
None.
Reason:
The specified user deleted a training session. The training session was set up by the specified user on the specified session.
Action:
None.
Reason:
The specified user updated a training session. The training session was set up by the specified user on the specified session.
Action:
None.
Reason:
The specified user deleted the second specified user from a training session. The training session was set up by the specified user on the specified session.
Action:
None.
Reason:
The ACB for the named virtual printer was successfully opened.
Action:
None.
Reason:
The ACB for the named virtual printer was successfully closed.
Action:
None.
Reason:
An error occurred during the open of the ACB for the named virtual printer.
Action:
See the ACB error flag meanings documented under the OPEN macro in IBM documentation on VTAM programming.
Reason:
An error occurred during the close of the ACB for the named virtual printer.
Action:
See the ACB error flag meanings documented under the CLOSE macro in IBM documentation on VTAM programming.
Reason:
This message appears only if the exit compatibility interface obtained from CA Technical Support is used. When TPX starts, this message always appears with EP=036. The address of the sender's UINDEX, ssssssss, and the address of the recipient's UINDEX, rrrrrrrr, will be 00000000. The address of the token is tttttttt. There is a flag that may be set in TPXOPER that causes this message to appear every time TPXUMAIL is called. From the TPXOPER command line, enter the following: D MEM,AREA=SMRT. Page down to offset 57B and set that byte to X'04' It will be X'00' before you do this. This message is for informational purposes only.
Action:
None.
Reason:
These messages are produced by an integrated debugging facility in the TPXUMAIL-TPXUBROD conversion facility. These message numbers are reserved. These messages are for informational purposes only.
Action:
None.
Reason:
The product has attempted to connect to the Coupling Facility structure. ssss indicates the structure name; cccc indicates the connection name; xxxx indicates the return code associated with the request; yyyy indicates the reason code associated with the request ddd; indicates the Status of the Structure; NEW indicates that the Structure was created by this request; OLD indicates that the Structure previously existed. nnnnnnnn is the approximate number of users the structure can support.
Action:
See IBM documentation for the meaning of the return and reason codes. This message is informational and does not necessarily indicate a problem. The error codes may be useful in diagnosing problems related to coupling facility connectivity.
Reason:
This message is informational. It indicates the progress of Coupling Facility structure allocation.
Action:
None
Reason:
An error has occurred during Coupling Facility structure allocation. VTAM generic resource support will not be available.
Action:
See message TPXL5130 for specific details on the error.
Reason:
This message is informational. It indicates the progress of Coupling Facility structure allocation.
Action:
None
Reason:
An error has occurred during Coupling Facility structure allocation. VTAM generic resource support will not be available.
Action:
See message TPXL5130 for specific details on the error.
Reason:
This message is informational. It indicates the progress of Coupling Facility structure allocation. llll is the list number being cleared
Action:
None
Reason:
An error has occurred during Coupling Facility structure allocation. VTAM generic resource support will not be available.
Action:
See message TPXL5130 for specific details on the error.
Reason:
An error has occurred during Coupling Facility structure allocation. VTAM generic resource support will not be available.
Action:
See message TPXL5130 for specific details on the error.
Reason:
An error has occurred during Coupling Facility structure allocation. VTAM generic resource support will not be available.
Action:
See message TPXL5130 for specific details on the error.
Reason:
An error has occurred during Coupling Facility structure allocation. VTAM generic resource support will not be available.
Action:
See message TPXL5130 for specific details on the error.
Reason:
One or more items (such as the Mail Data set) are not the same for all instances of the product operating with this generic resource name.
Action:
Review the explanations associated with messages TPXL5113, TPXL5114, and TPXL5115. Correct the discrepancies and restart this instance of the product.
Reason:
The maximum number of Instances for this generic resource has already connected to the Structure. No additional instances may connect to this structure. VTAM generic resource support for this instance will not be available.
Action:
Increase the Generic Resource Member Count on panel TEN0270 for all members of this generic resource group. Bring down all members and then restart members as necessary.
Reason:
Following is the contents of the Master List Entry in the Coupling Facility structure. This message is followed by message TPXL5115 showing the details.
Action:
See message TPXL5111 for an explanation of why this occurred and action to be taken.
Reason:
Following is the contents of the Master List Entry as expected by this instance. This message is followed by message TPXL5115 showing the details.
Action:
See message TPXL5111 for an explanation of why this occurred and action to be taken.
Reason:
This message identifies the information being compared for all instances of the product running with the same generic resource name and connected to this structure. The information must be the same for instances of the product.
xxxx identifies the variable being displayed:
dddd indicates the value for specific variable.
Action:
Review the explanation of messages TPXL5113 TPXL5114 and TPXL5111. Correct any discrepancies and restart this instance of the product.
Reason:
This message is informational. It indicates the progress of Coupling Facility structure allocation. llll is the list number being allocated.
Action:
None
Reason:
This message is informational. It indicates the progress of Coupling Facility structure allocation.
Action:
None
Reason:
This message is informational. It indicates the progress of Coupling Facility structure allocation.
Action:
None
Reason:
During initialization, a number of unsuccessful attempts were made to lock a List in the Coupling Facility. The lock is being held by the system. The product will not use the structure, nor will it use VTAM generic resource support.
Action:
Review the error codes previously provided by message TPXL5130, which occurs once per attempt. Determine who is holding the Lock and rectify the problem. Restart the affected instance of the product.
Reason:
An event has occurred associated with a Coupling Facility structure that the product is connected to. The product does not recognize the event code identified by cccc. The connection name that is the subject of the event is identified by nnnn.
Action:
See IBM documentation for the meaning of the event code. This message is informational and does not necessarily indicate a problem. The error codes may be useful in diagnosing problems related to coupling facility connectivity.
Reason:
The product has just connected to structure ssss. The product is being notified of a previous existing connection to this structure by the name of nnnn. This message is informational.
Action:
None.
Reason:
The product is currently connected to structure ssss in the Coupling Facility. A new connection have been made to this structure by is known by connection name nnnn. This message is informational.
Action:
None
Reason:
The product is currently connected to structure ssss in the coupling facility. A connection by the name of nnnn has disconnected from this structure and has indicated an error condition exists. This instance of the product will ensure entries in the coupling facility structure related to failed system will be deleted. This message is informational.
Action:
None
Reason:
The product is currently connected to structure ssss in the coupling facility. A connection by the name of nnnn has disconnected from this structure for normal reasons (such as shutdown). This message is informational.
Action:
None
Reason:
The instance of the product connected to structure ssss with connection name nnnn has lost connectivity to the structure. If this instance of the product is the affected instance, a Disconnect Failure Request will be attempted; VTAM generic resource support will be impaired. This message is informational.
Action:
Determine why the connection failed and correct any problem. Restart the affected instance of the product.
Reason:
The product that is connected to structure ssss by the name nnnn is being notified that the named structure has failed. A Disconnect Failure Request will be attempted. VTAM generic resource support will be impaired.
Action:
Determine why the connection failed and correct any problem. Restart the affected instance of the product.
Reason:
The product is connected to structure ssss with connection name nnnn. The volatility state of this structure has changed. The current state of volatility is indicated by vvvv. Possible values are VOLATILE and NON-VOLATILE. This message is informational.
Action:
None.
Reason:
The product is in the process of updating the coupling facility structure for a failed system. This message indicates the progress of this process. See message TPXL5123 for an additional explanation.
Action:
None.
Reason:
The product is in the process of updating the coupling facility structure for a failed system. This message indicates the progress of this process. llll indicates the number of the List being cleared. See message TPXL5123 for an additional explanation.
Action:
None.
Reason:
A request was issued to the Coupling Facility. This message indicates the relative success of the request and is not necessarily indicative if a problem. ffff identifies the function requested. rrrr indicates the return code associated with the request. ssss indicates the reason code associated with the request. llll indicates the List Number associated with the request. eeee indicates the entry name associated with the request.
Action:
See IBM documentation for the meaning of the return and reason codes. This message is informational and does not necessarily indicate a problem. The error codes may be useful in diagnosing problems related to coupling facility connectivity.
Reason:
An asynchronous Coupling Facility request has completed.xxxxx indicates the return code. yyyyy indicates the reason code.
Action:
See IBM documentation for the meaning of the return and reason codes. This message is informational and does not necessarily indicate aproblem (even if codes are non-zero). This information may be useful indiagnosing other related problems.
Reason:
The product has attempted to disconnect for normal reasons from the Coupling Facility structure. rrrr indicates the return code associated with the request. ssss indicates the reason code associated with the request. This message may appear as part of the shutdown process.
Action:
See IBM documentation for the meaning of the return and reason codes. This message is informational and does not necessarily indicate a problem. The error codes may be useful in diagnosing problems related to coupling facility connectivity.
Reason:
The product has attempted to disconnect due to some abnormal condition from the Coupling Facility structure. rrrr indicates the return code associated with the request. ssss indicates the reason code associated with the request. The abnormal condition may or may not be related to Coupling Facility.
Action:
See IBM documentation on Sysplex Services for the meaning of the return and reason codes. This message is informational and does not necessarily indicate a problem. The error codes may be useful in diagnosing problems related to Coupling Facility connectivity.
Reason:
A system-managed rebuild for the CA TPX structure yyyyyyy has been started by operations.
Action:
None.
Reason:
A system-managed rebuild for the CA TPX structure yyyyyyy has been completed.
Action:
None.
Reason:
An alter structure request has been initiated for the CA TPX structure yyyyyyy.
Action:
None.
Reason:
An alter structure request for the CA TPX structure yyyyyyy has been completed.
Action:
None.
Reason:
A system-managed rebuild request has been stopped by operations for the CA TPX structure yyyyyyy.
Action:
None.
Reason:
A Connect request to structure yyyyyyy for the connector zzzzzz has been denied because a system-managed rebuild or alter is in progress. Retry will be attempted.
Action:
None.
Reason:
Due to a structure outage, signons are not currently allowed.
Action:
None.
Reason:
The current TPX, named nnnn, is attempting to reconnect to the Coupling Facility structure, following a structure outage.
Action:
None.
Reason:
The current TPX, named nnnn, has successfully reconnected to the Coupling Facility structure. It has started the process of rebuilding the necessary data to continue processing as part of the Generic Resource pool.
Action:
None.
Reason:
The current TPX, named nnnn, has successfully completed the process of rebuilding the necessary data to continue processing as part of the Generic Resource pool.
Action:
None.
Reason:
All members of the Generic Resource pool have completed rebuilding their Coupling Facility data and signons are once again allowed.
Action:
None.
Reason:
The remote TPX, named rrrr, is attempting to reconnect to the Coupling Facility structure, following a structure outage.
Action:
None.
Reason:
The remote TPX, named rrrr, has successfully reconnected to the Coupling Facility structure. It has started the process of rebuilding the necessary data to continue processing as part of the Generic Resource pool.
Action:
None.
Reason:
The remote TPX, named rrrr, has successfully completed the process of rebuilding the necessary data to continue processing as part of the Generic Resource pool.
Action:
None.
Reason:
The task that manages the Coupling Facility Requests has been started. This message typically occurs during startup.
Action:
None.
Reason:
The task that manages the Coupling Facility Requests in now terminating. This message normally occurs during shutdown.
Action:
None.
Reason:
The task that manages the Coupling Facility requests has ended.
Action:
None.
Reason:
The Coupling Facility Manager Task was posted with an event it did not recognize. The event code is indicated by ccccc.
Action:
This is not a normal condition and indicates a programming error. Notify CA Technical Support of this message. Additional documentation may be requested.
Reason:
The connect request to the Coupling Facility failed. Sysplex Services will not be available.
Action:
Review message TPXL5101 and determine why failure occurred.
Reason:
The structure name was not properly supplied. The connection will not be attempted. Sysplex Services will not be available.
Action:
Review documentation and supply a structure name.
Reason:
The product is in the process of cleaning up the structure for a failed instance. An Unlock Request has failed and the recovery will be abandoned by this instance of the product.
Action:
See message TPXL5130 for more specific information on the failure.
Reason:
The product issued a Disconnect Request to the Coupling Facility. The request failed. Processing continues. This may occur during shutdown or recovery processing.
Action:
See message TPXL5131 or TPXL5132.
Reason:
A z/OS or OS/390 Resume request was issued and ended with a non-zero return code. cccc indicates the value of the return code.
Action:
See IBM documentation for the meaning of this return code.
Reason:
The coupling facility manager task was called to disconnect from the coupling facility with an invalid token or type function.
Action:
Contact CA Technical Support.
Reason:
The instance of the product is already connected to the cross-system Coupling Facility (XCF). This message may occur during recovery processing.
Action:
None.
Reason:
The product is in the recovery process for a failed instance. It has determined another instance of the product and has already enqueued the recovery lock for the failed instance. Recovery will be abandoned by this instance.
Action:
None.
Reason:
The product is in the process of cleaning up the structure for a failed instance. A Lock Request was issues and completed in error. See message TPXL5130 for more specific information regarding this error. The recovery process will be abandoned by this instance of TPX. Another instance of TPX may successfully process the recovery.
Action:
None.
Reason:
The product is in the process of cleaning up the structure for a failed instance of the product. cccccccc identifies the connection name of the failed system.
Action:
None.
Reason:
The product is in the process of cleaning up the structure for a failed instance. cccccccc identifies the connection name of the failed system. The Index Entry for the failed instance could not be located. This may be due other problems. This message is provided for informational purposes.
Action:
None.
Reason:
CA TPX is performing Coupling Facility list recovery for a peer instance that has abruptly disconnected from the structure. The list number cleared is identified by nnnn.
Action:
None.
Reason:
The product is in the process of cleaning up the structure for a failed instance. A Delete_Mult Request has failed and the recovery will be abandoned by this instance.
Action:
See message TPXL5130 for more specific information on the failure.
Reason:
The product has completed the recovery process for a failed instance identified by connection name cccc. The return code and reason code of the final request associated with the recovery are indicated by xxxx and yyyy respectively.
Action:
None
Reason:
During initialization, a number of unsuccessful attempts have been made to lock a List in the Coupling facility. The product will not use the structure, nor will it use VTAM generic resource support.
Action:
Review the error codes previously provided by message TPXL5130, which occurs once per attempt. Determine who is holding the Lock and rectify the problem. Restart the affected instance.
Reason:
This is an informational message noting that the global router task has started.
Action:
None.
Reason:
This is an informational message noting that a Global TPXOPER session has been started for terminal tttttttt on TPX system ssssssss.
Action:
None
Reason:
This is an informational message noting that a Global TPXOPER session has ended for terminal tttttttt on TPX system ssssssss.
Action:
None
Reason:
This is an informational message noting that the Internet Protocol service task has been started.
Action:
None.
Reason:
This is an informational message noting that the Logmode Table named nnnnnn has been loaded into memory that will be used with the IP interface.
Action:
None.
Reason:
The IP service task has encountered an error condition loading the Logmode Table that would be used in conjunction with the IP interface. This is a critical error. IP services will not be available.
Action:
Check the log for a message (TPXL5317 to TPLX5321) for additional information relating to the error condition.
Reason:
This is an informational message that the Internet Protocol service task has successfully initialized.
Action:
None.
Reason:
This is an informational message that the Internet Protocol service task has initialized the cross-memory communication interface.
Action:
None.
Reason:
This is an informational message indicating the task is waiting for the next event.
Action:
None.
Reason:
This is an informational message indicating the task received an event and will process it.
Action:
None.
Reason:
This is an informational and diagnostic message indicating the task received an invalid event.
Action:
None.
Reason:
This is an informational message indicating that the IP service task has been posted for termination.
Action:
None.
Reason:
This is an informational message indicating the task received an IP-end event. However, the address received in event does not match the address of IP-ACB. The event is ignored.
Action:
None.
Reason:
This is an informational message indicating the IP service task has begun the shutdown process.
Action:
None.
Reason:
This is an informational message indicating the IP service task is shutting down. The SMRT option Activate TCPaccess Telnet Interface is not enabled.
Action:
None.
Reason:
The TCPaccess Telnet Server interface requires APF Authorization. CA TPX has determined it is not running as an APF authorized program and will not enable the interface.
Action:
For information concerning authorization, see the Installation Guide and Administration Guide.
Reason:
The CA TPX IP service task failed in building critical structures needed for loading the Application Program Interface (API). The IP service task will shut down. IP services will not be available.
Action:
Check the log, JES job log, and the system log for the appropriate messages indicating the failing component or reason.
Reason:
The CA TPX IP service task has ended. IP services are no longer available.
Action:
None.
Reason:
The CA TPX IP service task could not locate the ddname nnnnnnnn. This is a critical error. IP services will not be available.
Action:
Add the necessary DD statement to the JCL. Recycle the product.
Reason:
Open failed for ddname nnnnnnnn. This is a critical error. IP services will not be available.
Action:
Check the data set pointed to by ddname nnnnnnn. Ensure it is available and in the appropriate data set organization (PDS, flat file, and so on) as described in the CA TPX documentation. Recycle the product.
Reason:
The CA TPX IP service task could not find the Logmode Table nnnnnnnnn as member of the library pointed to by the VTAMLIB DD statement. This is a critical error. IP services will not be available.
Action:
Ensure that the Logmode Table name given by MODETAB= JCL parameter or the default, ISTINCLM, is a member in the library data set pointed to by the VTAMLIB DD statement. Recycle CA TPX.
Reason:
An error occurred when CA TPX attempted to load the Logmode Table nnnnnnnn from the library pointed to by ddname VTAMLIB. This is a critical error. IP services will not be available.
Action:
Reason:
CA TPX IP service task has encountered an error during CLOSE of the library referenced by ddname nnnnnnnn.
Action:
Check the JES job log and system log for the operating system message that indicates the error.
Reason:
This is an informative message to confirm the status of connecting to XCF at startup.
Action:
None
Reason:
The product could not connect to XCF due to insufficient main storage.
Action:
Increase region size and restart.
Reason:
This is an informative message to confirm disconnecting of the product from XCF.
Action:
None
Reason:
The product has successfully initialized XCF and XES Services. nnnnnnnn identifies the system ID of the node.
Action:
None.
Reason:
The product has terminated XCF and XES Services. nnnnnnnn identifies the system ID of the node.
Action:
None.
Reason:
Message transmission through XCF has failed.
Action:
See your z/OS guide to determine the correct action based on the code you receive.
Reason:
Query of XCF for connected systems failed.
Action:
See your z/OS guide to determine the correct action based on the code you receive.
Reason:
Receiving an incoming XCF message failed.
Action:
See your z/OS guide to determine the correct action based on the code you receive.
Reason:
The MAIL facility failed to receive an incoming mail message.
Action:
Check the log for any XCF error messages with more specific status information.
Reason:
The MAIL facility received an invalid message buffer through XCF. A system dump is taken to help detect the nature of the failure.
Action:
None
Reason:
Failure processing incoming Global Router message buffer through XCF.
Action:
Check the log for any XCF error messages with more specific status information.
Reason:
The Global Router facility received an invalid message buffer through XCF. A system dump is taken to help detect the nature of the failure.
Action:
None
Reason:
The specified user has signed on with a security system that requires a SAMT, but none could be found or loaded. This message is also written to the system log. The variable sectype has a value of RACF, SAF, ACF2, or TOPS.
Action:
Specify the correct SAMT in online administration or the startup procedure.
Reason:
The specified user has signed on and received a return code or message from the security system that is not in the SAMT. The variable code has the value of either the return code or message ID that was not found.
Action:
Add the return code to the SAMT.
Reason:
The product cannot find the CA‑ACF2 CVT with the information specified in System Options "CVT Location and CVT Offset" (on panel TEN0090). Because the product cannot always determine if the address is correct or not, a possible result could be a SOC4 abend. This message is also written to the system log.
Action:
Check with your CA‑ACF2 systems programmer to make sure it is set up correctly.
Reason:
he specified user has signed on using user-level profile selection (other than for CA‑ACF2), and a group specified on the user's security record does not match any profiles. This message will only be displayed as a diagnostic zap.
Action:
None.
|
Copyright © 2013 CA.
All rights reserved.
|
|