 |
» |
|
|
|
APPC logging messages are returned during subsystem startup
and while the subsystem is active. There are five classes of events that can be logged for the
APPC subsystem (SUB0016). They are as follows: CLAS0010 records internal errors. CLAS0011 records subsystem warnings. CLAS0012 records subsystem information messages. CLAS0013 records conversation information messages. CLAS0014 records session performance statistics.
These messages are returned to the system console, a user
terminal, or a disk file, depending upon what you have configured
in the NMCONFIG file for logging. MESSAGE: APPC: Subsystem Started (APPCLOG
0). | CAUSE: The control operator has completed subsystem startup. ACTION: No action required. |
MESSAGE: APPC: Subsystem Stopped (APPCLOG
1). | CAUSE: The subsystem has completely shut down. ACTION: No action required. |
MESSAGE: APPC: ! | CAUSE: APPC performance data for APPC subsystem. These
messages appear when the APPCCONTROL PERFORMANCE command is issued. See the description of APPCCONTROL PERFORMANCE for examples. ACTION: No action required. |
MESSAGE: APPC: ! | CAUSE: APPC performance data for each active session.
These messages appear when the APPCCONTROL PERFORMANCE command is issued. See the description of APPCCONTROL PERFORMANCE for examples. ACTION: No action required. |
MESSAGE: APPC: Session Started, Session
ID=! (APPCLOG 6). | CAUSE: An APPC session with the specified Session ID
number has started. This session is now available for use by transaction
programs. ACTION: No action required. |
MESSAGE: APPC: Session Stopped, Session
ID=!, Reason=! (APPCLOG 7). | CAUSE: An APPC session with the specified Session ID
number has been stopped (unbound) due to the Reason given. (Reasons
can include APPC_Kill, APPC_Protocol, APPC_Quiesce, Host_Unbind, Link_Failure,
SNA_Error, Convers_Abend, BIS_Error, CTLA_Shutdown, SNA_Kill, SNA_Protocol,
SNA_Quiesce, HS_Error, SM_Error, and RM_Error.) ACTION: If you suspect a problem, note the Reason and
contact your HP representative. |
MESSAGE: APPC: Bind Rejected, Session
ID=!, Sense Data=! (APPCLOG 8) | CAUSE: The session with the specified Session ID could
not be established, because the local LU rejected the BIND from
the remote system. ACTION: Make sure the LUs are correctly configured on
the host. If the host configuration is correct, recreate the problem:
enable the SNA Transport link trace, and activate the APPC subsystem
again. Give the trace to your HP representative. |
MESSAGE: APPC: Init-Self Negative Rsp,
Session ID=!, Sense Data=! (APPCLOG 9). | CAUSE: The session with the specified Session ID could
not be established, because the host sent a negative response to
the INIT_SELF sent by the local LU. ACTION: There could be a problem with the remote system,
or the remote system might be down. The Remote LU Name specified
in the APPC subsystem configuration might be incorrect. If the remote
system is up, and the Remote LU Name is configured correctly, give
the SNA Transport intrinsic trace to your HP representative. |
MESSAGE: APPC: SNAOpenUser Failed,
Session ID=!, Result=! (APPCLOG 10). | CAUSE: SNA Transport was unable to establish a session
with the specified LU. ACTION: If SNA Transport is not active, issue the SNACONTROL START command to activate it. Check to make sure the LU or
LUs configured for the session type are not being used by another
SNA Service. The Result listed in the message is the number of an SNA
Transport error message; see the SNA Link/XL Node Manager's
Guide for more information. |
MESSAGE: APPC: SNA/LINK Error, Session
ID=!, Result=! (APPCLOG 11). | CAUSE: The APPC subsystem has encountered an error in
SNA/SDLC Link/XL. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: Received Notify, Session
ID=! (APPCLOG 12). | CAUSE: The remote system has sent an SNA NOTIFY command over the session with the specified Session ID. ACTION: This could occur (1) because of a problem with
the remote system, (2) because the remote application is not up,
(3) because the LU is not configured for use by the remote, or (4)
because the Remote LU Name specified in the configuration for the
session type is incorrect. If none of these is the case, give the
APPC subsystem internal trace to your HP representative. |
MESSAGE: APPC: SM Detected Error, Session
ID=!, Error=!, ! (APPCLOG 13). | CAUSE: The APPC subsystem has detected an internal error. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: Stray Negative Rsp,
Session ID=! (APPCLOG 14). | CAUSE: The APPC subsystem has detected a stray negative
response coming from the remote system. ACTION: No action required; however, if this occurs frequently,
it may affect the remote system. If other problems are occurring simultaneously,
notify your HP representative. |
MESSAGE: APPC: Stray Signal, Session
ID=! (APPCLOG 15). | CAUSE: The APPC subsystem has detected a stray SNA SIGNAL command coming from the remote system. ACTION: No action required; however, if this occurs frequently,
it may affect the remote system. If other problems are occurring simultaneously,
notify your HP representative. |
MESSAGE: APPC: HS Detected Error, Session
ID=!, Error=! (APPCLOG 16). | CAUSE: The APPC subsystem has detected an internal error. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: TP started, TPName=!,
TCB ID=! (APPCLOG 17). | CAUSE: A transaction program with the specified transaction
program name and Transaction Control Block ID (TCB ID) has been
started. ACTION: No action required. |
MESSAGE: APPC: TP stopped, TPName=!,
TCB ID=! (APPCLOG 18). | CAUSE: A transaction program with the specified transaction
program name and Transaction Control Block ID (TCB ID) has been
stopped. ACTION: No action required. |
MESSAGE: APPC: TP Abend, TPName=!,
TCB ID=! (APPCLOG 19). | CAUSE: A transaction program with the specified transaction
program name and Transaction Control Block ID (TCB ID) has been
aborted. ACTION: The transaction program has terminated abnormally.
Notify the TP programmer. |
MESSAGE: APPC: TP Start Failed: APPC
Subsystem not started (APPCLOG 20). | CAUSE: A transaction program could not be started because
the local APPC subsystem is not active. ACTION: Issue the command APPCCONTROL START to activate the APPC subsystem. |
MESSAGE: APPC: TP Local Attach Failed,
Reason=! (APPCLOG 21). | CAUSE: A transaction program could not be started because
the local attach failed. ACTION: Notify your HP representative. |
MESSAGE: APPC: TP Not Found in SL,
TPName=! (APPCLOG 22). | CAUSE: The transaction program name given could not be
found in the appropriate segmented library file. ACTION: Notify your HP representative. |
MESSAGE: APPC: Remote Attach Failed:
TPName=! Not Found (APPCLOG 23). | CAUSE: The APPC subsystem could not find the requested
TP Name in the configuration file. ACTION: Make sure the TP Name is configured. Make sure
the TP Name passed by the remote TP in the allocate request matches
the configured TP Name. |
MESSAGE: APPC: Remote Attach Failed:
TPName=! Creation Failed (APPCLOG 24). | CAUSE: The APPC subsystem was unable to stream the job
to start up the local TP. ACTION: Make sure the job name is configured correctly
through NMMGR and that the configured job file exists. Make sure
there are no lockwords on the job file. |
MESSAGE: APPC: Conversation Started,
TCB ID=!, RCB ID=! (APPCLOG 25). | CAUSE: A conversation has been started on the transaction
program specified by the Transaction Control Block ID (TCB ID),
with the appropriate conversation ID (Resource Control Block ID
[RCB ID]). ACTION: No action required. |
MESSAGE: APPC: Conversation Stopped,
TCB ID=!, RCB ID=! (APPCLOG 26). | CAUSE: A conversation has been stopped on the transaction
program specified by the Transaction Control Block ID (TCB ID),
with the appropriate conversation ID (Resource Control Block ID
[RCB ID]). ACTION: No action required. |
MESSAGE: APPC: Conversation Abend,
TCB ID=!, RCB ID=! (APPCLOG 27). | CAUSE: A conversation has been aborted on the transaction
program specified by the Transaction Control Block ID (TCB ID),
with the appropriate conversation ID (Resource Control Block ID
[RCB ID]). ACTION: A conversation has terminated abnormally. Notify
the TP programmer. |
MESSAGE: APPC: Presentation Services
Detected Error, Error=! (APPCLOG 28). | CAUSE: The APPC module PS (Presentation Services) has
detected an internal error. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: Object dumped to file
! (APPCLOG 29). | CAUSE: The module COPR (Control Operator) has dumped
the APPC Object to the file specified. ACTION: This file and the APPC subsystem internal trace
file should be given to your HP representative. |
MESSAGE: APPC: Half Session Creation
Error, SUBSYS=!, INFO=! (APPCLOG 30). | CAUSE: The APPC subsystem was unable to create the Half
Session process ACTION: Contact your HP representative. |
MESSAGE: Resource Manager Creation
Error, NMError=! (APPCLOG 31). | CAUSE: The APPC subsystem was unable to create the Resource Manager
process. ACTION: Verify that the program file RM.APPC.SYS exists |
MESSAGE: APPC: Session Manager Creation
Error, NMError=! (APPCLOG 32). | CAUSE: The APPC subsystem was unable to create the Session Manager
process. ACTION: Verify that the program file SM.APPC.SYS exists. |
MESSAGE: APPC: COPRTP Creation Error,
NMError=! (APPCLOG 33). | CAUSE: The APPC subsystem was unable to create the COPRTP process. ACTION: Verify that the program file COPRTP.APPC.SYS exists. |
MESSAGE: APPC: CNOSTP Creation Error,
NMError=! (APPCLOG 34). | CAUSE: The APPC subsystem was unable to create the CNOSTP process. ACTION: Verify that the program file CNOSTP.APPC.SYS exists. |
MESSAGE: APPC: Control Operator Internal
Error, Error=! (APPCLOG 35). | CAUSE: The APPC module COPR (Control Operator) has detected
an internal error. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: Resource Manager Internal
Error, Error=! (APPCLOG 36). | CAUSE: The APPC module RM (Resource Manager) has detected
an internal error. ACTION: Give the APPC subsystem internal trace to your HP representative. |
MESSAGE: APPC: Session Manager Internal
Error, Error=! (APPCLOG 37). | CAUSE: The APPC module SM (Session Manager) has detected
an internal error. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: Half Session Internal
Error, Error=! (APPCLOG 38). | CAUSE: The APPC module HS (Half Session) has detected
an internal error. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: COPRTP Internal Error,
Error=! (APPCLOG 39). | CAUSE: The APPC module COPRTP (Control Operator TP) has
detected an internal error. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: CNOSTP Internal Error,
Error=! (APPCLOG 40). | CAUSE: The APPC module CNOSTP (Change-Number-Of-Sessions
TP) has detected an internal error. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: Control Operator Non-Fatal
Error: INFO=!, SUBSYS=! (APPCLOG 41). | CAUSE: The Control Operator encountered a non-fatal error.
The INFO value in the message is the number of a warning
or informational message. The SUBSYS value indicates which subsystem generated the message.
If SUBSYS=732, the message was generated by the APPC subsystem. ACTION: Note the INFO and SUBSYS values, and notify your HP representative. |
MESSAGE: APPC: Resource Manager Non-Fatal
Error: INFO=!, SUBSYS=! (APPCLOG 42). | CAUSE: The Resource Manager encountered a non-fatal error.
The INFO value in the message is the number of a warning
or informational message. The SUBSYS value indicates which subsystem generated the message.
If SUBSYS=732, the message was generated by the APPC subsystem. ACTION: Note the INFO and SUBSYS values, and notify your HP representative. |
MESSAGE: APPC: Session Manager Non-Fatal
Error: INFO=!, SUBSYS=! (APPCLOG 43). | CAUSE: The Session Manager encountered a non-fatal error.
The INFO value in the message is the number of a warning
or informational message. The SUBSYS value indicates which subsystem generated the message.
If SUBSYS=732, the message was generated by the APPC subsystem. ACTION: Note the INFO and SUBSYS< values, and notify your HP representative. |
MESSAGE: APPC: Half Session Non-Fatal
Error: INFO=!, SUBSYS=! (APPCLOG 44). | CAUSE: Half Session encountered a non-fatal error. The INFO value in the message is the number of a warning
or informational message. The SUBSYS value indicates which subsystem generated the
message. If SUBSYS=732, the message was generated by the APPC subsystem. ACTION: Note the INFO and SUBSYS values, and notify your HP representative. |
MESSAGE: APPC: COPRTP Non-Fatal Error:
INFO=!, SUBSYS=! (APPCLOG 45). | CAUSE: The COPRTP encountered a non-fatal error. The INFO value in the message is the number of a warning
or informational message. The SUBSYS value indicates which subsystem generated the
message. If SUBSYS=732, the message was generated by the APPC subsystem. ACTION: Note the INFO and SUBSYS values, and notify your HP representative. |
MESSAGE: APPC: CNOSTP Non-Fatal Error:
INFO=!, SUBSYS=! (APPCLOG 46). | CAUSE: The CNOSTP encountered a non-fatal error. The INFO value in the message is the number of a warning
or informational message. The SUBSYS value indicates which subsystem generated the
message. If SUBSYS=732, the message was generated by the APPC subsystem. ACTION: Note the INFO and SUBSYS values, and notify your HP representative. |
MESSAGE: APPC: PRIMARY STATUS: INFO=!,
SUBSYS=! (APPCLOG 47). | CAUSE: This message follows another message and supplies
the subsystem number and the return code from the internal intrinsic
that failed. ACTION: See the message that was logged just before this
one for more information. |
MESSAGE: APPC: SECONDARY STATUS: INFO=!,
SUBSYS=! (APPCLOG 48). | CAUSE: This message follows another message and supplies
the subsystem number and the return code from the MPE XL intrinsic
that failed. ACTION: See the message that was logged just before this
one for more information |
MESSAGE: APPC: ! ! Limits Succeeded:
OK AS SPECIFIED (APPCLOG 49). | CAUSE: The requested session limits have been accepted
as specified; they were not negotiated. ACTION: No action required. |
MESSAGE: APPC: ! ! Limits Succeeded:
OK AS NEGOTIATED (APPCLOG 50). | CAUSE: The requested session limits have been negotiated
successfully. ACTION: No action required. |
MESSAGE: APPC: ! ! Limits Failed: UNRECOGNIZED
MODE NAME (APPCLOG 51). | CAUSE: The mode name for the remote LU does not match
the mode name for the local LU. ACTION: Check the APPC subsystem configuration to verify
that the mode name configured for the local LU is the same mode
name configured for the remote LU. |
MESSAGE: APPC: ! ! Limits Failed: MODE
SESSION LIMIT CLOSED (APPCLOG 52). | CAUSE: The session limit on the IBM AS/400 was set to
0, and the APPC subsystem attempted to raise the session limit. ACTION: Start the mode on the AS/400. |
MESSAGE: APPC: ! ! Limits Failed: COMMAND
RACE REJECT (APPCLOG 53). | CAUSE: CNOS requests from both the local and the remote
systems attempted to change the session limits at the same time.
One or both requests failed. ACTION: Reissue the APPCCONTROL SESSIONS command. If this error occurred at subsystem startup,
restart the APPC subsystem. |
MESSAGE: APPC: ! ! Limits Failed: TRANSACTION
FAILURE (APPCLOG 54). | CAUSE: Internal error in CNOSTP or COPRTP. ACTION: Give the internal trace to your HP representative. |
MESSAGE: APPC: ! ! Limits Failed: SESSION
OUTAGE OCCURRED (APPCLOG 55). | CAUSE: The APPC session ended unexpectedly during a CNOSTP
or COPRTP conversation. ACTION: Use the APPCCONTROL STATUS command, specifying STYPE=SNASVCMG, to verify that a CNOS session is active. |
MESSAGE: APPC: ! ! Limits Failed: NO
CNOS SESSION AVAILABLE (APPCLOG 56). | CAUSE: No sessions are available for the CNOSTP. ACTION: Restart the APPC subsystem. Issue the APPCCONTROL STATUS command, specifying STYPE=SNASVCMG, to verify that CNOS sessions are active. |
MESSAGE: APPC: ! ! Limits Failed: CHANGE
SESSIONS FAILURE (APPCLOG 57). | CAUSE: Internal APPC subsystem error. ACTION: Give the internal trace to your HP representative. |
MESSAGE: APPC: ! ! Limits Failed: RESOURCE
FAILURE NO RETRY (APPCLOG 58). | CAUSE: A CNOSTP or COPRTP conversation failed. The session
might have failed, or the TP on the remote system might have encountered
an error and deallocated the conversation. ACTION: Reissue the APPCCONTROL SESSIONS command, or restart the APPC subsystem. |
MESSAGE: APPC: ! ! Limits Failed: UNKNOWN
ERROR (APPCLOG 59). | CAUSE: An error has occurred in the CNOSTP or COPRTP. ACTION: Give the APPC subsystem internal trace to your
HP representative. |
MESSAGE: APPC: Stype=!, Mode=!, Limit=!,
Source=!, Target=! (APPCLOG 60). | CAUSE: A CNOS (Change-Number-Of-Sessions) transaction
completed successfully. This message follows message APPCLOG 49
or APPCLOG 50 and supplies more information. ACTION: No action required. |
MESSAGE: APPC: Stype=!, Mode=! (APPCLOG
61). | CAUSE: A CNOS (Change-Number-Of-Sessions) transaction
failed. This message follows a message from APPCLOG 51 through APPCLOG
59 and supplies more information. ACTION: See the message that was logged just before this
one for more information. |
|
