z/OS MVS Using the Subsystem Interface
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Input Parameters

z/OS MVS Using the Subsystem Interface
SA38-0679-00

Input parameters for the function routine are:
  • SSOB
  • SSIB
  • SSNU
SSOB Contents: The caller sets the following fields in the SSOB control block on input:
Field Name
Description
SSOBID
Identifier 'SSOB'
SSOBLEN
Length of the SSOB (SSOBHSIZ) control block
SSOBFUNC
SSI function code 75 (SSOBSSNU)
SSOBSSIB
Address of the SSIB control block or zero (If this field is zero, the life-of-job SSIB is used). See Subsystem Identification Block (SSIB) for more information on the life-of-job SSIB.
SSOBINDV
Address of the function dependent area (SSNU control block)

Set all other fields in the SSOB control block to binary zeros before issuing the IEFSSREQ macro.

SSIB Contents: If you don't use the life-of-job SSIB, the caller must provide an SSIB and set the following fields in the SSIB control block on input:
Field Name
Description
SSIBID
Identifier 'SSIB'
SSIBLEN
Length of the SSIB (SSIBSIZE) control block
SSIBSSNM
Subsystem name — name of the subsystem to which this Notify User Message Service call is directed. It is usually the primary JES, or in the case of JES2, a possible secondary JES.

If your routine has not been initiated from such a JES, the caller must issue a Request Job ID call (SSI function code 20) prior to this Notify User Message Service call. You must use the same subsystem name in this SSIBSSNM field as you used for the Request Job ID call.

SSIBSUSE
(JES3 only) Subsystem use — the SSIBSUSE value that was returned upon completion of the Request Job ID call (SSI function code 20).

The caller must set all other fields in the SSIB control block to binary zeros before issuing the IEFSSREQ macro.

SSNU Contents: The caller sets the following fields in the SSNU control block on input:
Field Name
Description
SSNUID
Identifier 'SSNU'
SSNULEN
Length of the SSNU (SSNUSIZE) control block
SSNUVER
Version of mapping for the caller — Set this field to SSNUCVER (an IBM-defined integer constant within the SSNU control block).
SSNUFLG1
Flag Byte
  • SSNU1MLO — logon message flag

    If SSNU1MLO is set, a message is issued only if the user is logged on.

SSNUTKNA
Associated security token of issuing user. This field is optional, and is only valid for authorized callers. For unauthorized callers, the value will be ignored and a reason code (SSNUERCD) of 40 (SSNUUNTK) will be set.

If not specified, or ignored, a security token is extracted using the caller's security environment.

If the message is not destined for the home (local) node, the security token is passed on a WRITER class RACROUTE AUTH call to validate that the user has the authority to issue messages to another NJE node.

If the message is destined for the home (local) node, the security token is passed on the SEND operator command to verify that the message can be delivered to the destination user.

SSNUNODE
Node on which messages are sent. For the home node, use the home node name or binary zeros in the SSNUNODE field. Do not use blanks (X'40') or an alias name (JES3) because they will not be treated as the home node name. If the destination is the home node, no WRITER class security checks are performed.
SSNUUSER
User ID to which messages are sent.
SSNUMLEN
Length of the message pointed to by the SSNUMSG field. The message must be no greater than 100 characters.
SSNUMSG
Address of the EBCDIC data message that is issued.
SSNUMEMB
Start of change Preferred JES2 member name to issue the SEND on if the user is logged on. If the user is not logged on, the SEND is issued locally. This field is not used by JES3 because the JES3 send is always issued from the global processor. End of change

Set all other fields in the SSNU control block to binary zeros before issuing the IEFSSREQ macro.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014