M204.2509

From m204wiki
Revision as of 17:26, 13 March 2018 by DmeWiccan (talk | contribs) (Automatically generated page update)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

M204.2509  token hexValue

Horizon uses this message to report two types of events:

  • A receipt of request or a response unit for sessions that are in the process of termination and are therefore discarded.
  • A failed attempt to BIND a session.

The general format of the message in the first case is:

M204.2509 rutype BEING DISCARDED FOR HS_ID = xxxxxxxx

or

M204.2509 DISCARDING rutype FOR HS_ID = xxxxxxxx

where HS_ID is the hexadecimal Half Session identifier and rutype is one of the following:

  • BIND RESPONSE
  • CINIT (Control Initiate) REQUEST
  • MESSAGE
  • NOTIFY REQUEST
  • TERMINATE REQUEST
  • UNBIND RESPONSE

The general format of the message in the second case is:

M204.2509 rutype FAILED | REJECTED SENSE=

where rutype is one of the following:

  • BIND
  • BIND RESPONSE

The sense codes are standard SNA codes, which are listed in the IBM manual SNA Formats, GA27-3136.

The following table is a sampling of sense codes:

Code

Message

Action to take (if any)

08050000

Session limit exceeded

Check the DEFINE PROCESSGROUP INLIMIT parameter, or

DEFINE SESSIONGROUP MAXIMUM and WINNERS parameters for CNOS.

08090000

Mode inconsistency (wrong state)

 

080F6051

Security violation

Check that the partner is opening the process with a valid user ID and password; check the LOGON and GUESTUSER parameters on the local and partner DEFINE PROCESSGROUP commands.

08150000

Function already active

 

0835nnnn

Parameter error in BIND image

 

084B0000

Resources are not available

Check storage to see if it is a problem.

08520001

Session activation request received while earlier one pending

 

System manager response: The DISCARDED messages usually point to some earlier session failure, and no further action is usually necessary.

When there is a BIND failure, check the BIND parameters--the MODENAME parameter on the DEFINE PROCESSGROUP or DEFINE SESSIONGROUP--on both ends of the session. Refer also to the previous table on specific sense codes.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=0Sets batch (single user) return code
CLASS=IInformation class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter
AUDITMSWrites the message with line type MS to the audit trail
NOCOUNTDoes not increment the error count (ERCNT) parameter

Back to list of messages