DFS070 diagnostic message

Diagnostic messages from DFS070 are described.

Here is an example of the DFS070 diagnostic message: 
DFS070 UNABLE TO ROUTE MESSAGE RSN=0104
The RSN code identifies the module that issued the message (01 = DFSICIO0) and the reason for the error (04 = Prefix buffer length is too large).

In this case DFSICIO0 called the message generator (DFSCLMR0) with R1 = 00680046. 

Where x'00680046' = module identifier, reason code,message key
                         x'0068' = 0104 (decimal)
                                    01 = Module that issued message = DFSICIO0
                                    04 = Prefix buffer length is too large

                         x'0046  = 70 (decimal) = DFS070 MESSAGE KEY

The following table shows:

  • The label used for the module identifier
  • The module identifier
  • The module function or name

The labels shown in the following table can be used to scan the module source code to locate where the message was issued from.

Table 1. DFS070 module identifier table
Label Default module identifier Function (module name)
MSUK 00 Unknown module or DFSMSCEC requestor
MSTR 01 DC Communication Manager (DFSICIO0)
MSTRAP 02 LU 6.2 Receive LU Manager (DFSRLM10)
MSTROT 03 OTMA Receive LU Manager (DFSYTIB0)
MSPR 04 DC Call Handler (DFSDLA30)
MSLR 05 MSC Analyzer (DFSCMS00)
MSFM 06 /FORMAT Command Processor (DFSICLK0)
MSTE 08 IMS Termination (DFSTRM00)
MSINIT 10 IMS Initialization (DFSIINB0)

The following table shows:

  • The label used for the reason code
  • The reason code value
  • The description of the error

The labels shown in the following table can be used to scan the module source code to locate where the message was issued from.

Table 2. DFS070 reason (RSN) codes table
Label Reason code decimal/hexadecimal Description
PFXUPRER 02/02 User requested 2 user prefix segments (code 8E).

Programmer response: The routine that was setting up to call the DFSMSCE0 user exit determined that a user prefix segment had already been obtained. The programmer may need to turn on the DFSMSCE0 trace to determine which routine is setting the field, MSCEUPR (DFSMSCEP) or the flag MSCEB2RET (DFSMSCEB).
PFXIPRER 03/03 User requested two Workload router prefix segments (code 8F).

Programmer response: The routine that was setting up to call the DFSMSCE0 user exit determined that a user prefix segment had already been obtained. The programmer may need to turn on the DFSMSCE0 trace to determine which routine is setting the field MSCEUPR (DFSMSCEP) or the flag MSCEB2RET (DFSMSCEB).
PFTOOBIG 04/04 Prefix buffer length is too large.

Programmer response: The user prefix segment size field MSCEUPRL (DFSMSCEP) or the workload router prefix segment size field MSCEIPRL (DFSMSCEP) is greater than 512. The programmer may need to turn on the DFSMSCE0 trace to determine which routine is setting the field MSCEUPR or MSCEIPR (DFSMSCEP) to a value larger than 512.
GBPFER 05/05 DFSPOOL error on get prefix buffer.

Programmer response: Failure to get storage for the user prefix segment or the workload router prefix segment through the DFSPOOL macro from the HIOP pool.
URCERR1 06/06 User exit return code negative.

Programmer response: User exit DFSMSCE0 returned a negative return code.
URCERR2 07/07 DFSBCB error getting BCB block.

Programmer response: User exit DFSMSCE0 returned a negative return code returned an invalid return code.
GMSBERR 08/08 DFSBCB error getting BCB block.

Programmer response: Failure to get storage for the MSEB block through the DFSBCB macro.
LRBADSID 09/09 Bad SYSID detected.

Programmer response: In getting the address for the LNB that is associated with either the origin SID or the SID that is specified by the caller, a bad SYSID was detected.
IPFX 10/0A Queue Manager insert prefix error.

Programmer response: In an effort to update the MESSAGE PREFIX (01/03) log record, a prefix update call was made (DFSQMGR0) to add the user prefix segment or the workload router segment, or both. The prefix update routine was unable to add the segment.
ICLR1ERR 11/0B Non zero return code from DFSICLR1 (DFSICLR0).
AVMLKERR 12/0C Destination is an invalid type for AVM/ISC link.
MSCEFL1E 15/0F DFSMSCEC user exit routing flag is in error.

Programmer response: An invalid option was requested for the user routing exit flag 1 (MSTRFL1/MSLRFL1/MSPRFL1). Refer to the DFSMSCEP macro for valid options. Check the user exit parameter in the 6701-MSCE record to determine which option was requested. These options are usually set by IMS code.
USRXIFER 16/10 DFSUSRX interface error.

Programmer response: The macro DFSMSCEC invoking DFSUSRX0 through the DFSUSRX macro received a non-zero return code. The value is in field MSCEBRC in the DFSMSCEB block. Possible values returned are:

  1. 04 the user exit routine specified has not been defined (the address in UXDT is zero)
  2. Unable to get an interface block using the DFSBCB macro. DFSBCB return code is in field, MSCEBSSRC in the DFSMSCEB block.
IONAMCHG 18/12 User exit changed the destination name of the I/O PCB message.

Programmer response: The user exit (DFSMSCE0) set flag MSPR2CHG in field MSPRFL2 to request that the destination name MSPRDEST be changed. The PCB is the I/O PCB that cannot be changed. Check the user exit parameter in the 6701-MSCE record to determine which option was requested.
IOROUTE 19/13 User exit requested reroute I/O PCB message.

Programmer response: The user exit DFSMSCE0 requested a routing option of MSPR2RMT, /MSPR2LSQ, /MSPR2SRC, /MSPR2NDR in field MSPRFL2. This is invalid if the PCB is the I/O PCB.

Refer to the user exit parameter in the 6701-MSCE record to determine which command was requested.
CMDINV 20/14 User exit changed the destination name to a command (such as: /CMDVERB).

Programmer response: The user exit DFSMSCE0 changed the destination name to a command.

Refer to the user exit parameter in the 6701-MSCE record to determine which command was requested.
SQGINV 21/15 User Link receive exit override MSNAME in segment because destination is not an MSNAME.

Programmer response: User exit DFSMSCE0 in a shared queues group link receive exit failed due to the destination not being an MSNAME.
REGFAIL 22/16 Local shared queue registration (DFSSQIF FUNC=INFRM) failed for the transaction when the user exit requested MSLR2LSQ=1 or MSTR2LSQ=1.
NOTRANCD 23/17 Terminal routing exit routed the message to a remote IMS (MSTR2RMT=1) but the destination type at MSTRDEST is an unsupported TRANCODE (such as remote routing is not allowed for LTERM or FAST PATH exclusive TRANCODE).
DSIDINV 24/18 The Terminal, Link Receive or the Program Routing exit returned an invalid destination SYSID (for example, either field MSTRDSID, MSLRDSID, or MSPRDSID is invalid).
DMSNINV 25/19 The Terminal, Link Receive, or Program routing exit returned an invalid destination MSNAME (for example: either field, MSTRDMSN, MSLRDMSN, or MSPRDMSN is invalid).
SSIDINV 26/1A The Link Receive exit rerouted an intermediate message (MSLR1INT=1) to this local IMS by setting MSLR2LOC=1, but the message had an invalid return (source) SYSID so this IMS could not accept it locally.
RMT2INV 27/1B The Terminal, Link Receive, or Program routing exit indicated routing the message to a remote MSC link by setting MSTR2RMT, MSLR2RMT, or MSPR2RMT; however, the exit did not set either of the corresponding destination SYSID or MSNAME fields (for example, either MSTRDSID, MSLRDSID, or MSPRDSID was left set to zero, or MSTRDMSN, MSLRDMSN, or MSPRDMSN was left set to blanks).
SRC2INV 28/1C The Program routing exit requested the message be routed to the source MSC system by setting MSPR2SRC=1 however the message cannot be routed because either:
  • MSC is not available.
  • Or the source SYSID is not valid because the application program has not issued a get unique (GU).
  • The application program is a non-message driven BMP.
NDR2INV 29/1D The Program Routing exit requested a direct routing message be overridden by setting MSPR2NDR=1; however, either:
  • MSC is not available.
  • This is not a direct routed message with a MSNAME destination.
  • The overriding name in the front of the I/O area is not valid.
RMT2FSR 30/1E The Terminal routing exit indicated to route the message to a remote MSC link by setting MSTR2RMT=1, but the input ISC node was set to process the message as a Front End Switch message by the user Front End Switch exit (DFSFEBJ0). Front End Switch messages cannot be routed to MSC links.
RSPROUTE 31/1F The Link receive exit requested that a response message (MSLR1RSP=1) be rerouted by either setting one of the MSLRFL2 reroute flags. Response messages may not be rerouted.
INBCHGID 33/21 CHANGEID not supported.

Programmer response: The user exit (DFSMSCE0) did not use the DFSMSCSV macro or generate module entry code. IMS initialization expects a branch instruction around the character information of entry code.

Refer to the sample version of the provided user exit DFSMSCE0's use of DFSMSCSV for more information.
INBIDLNG 35/23 Character string 'VECTOR' not present.

Programmer response: The user exit (DFSMSCE0) did not use the DFSMSCSV macro or generate module entry code. IMS initialization expects the entry code to contain a length of the module entry code at a given offset.

Refer to the sample version of the provided user exit DFSMSCE0's use of DFSMSCSV for more information.
INBNVECT 35/23 Character string 'VECTOR' not present.

Programmer response: The user exit DFSMSCE0 did not use the DFSMSCSV macro or module entry code to provide the character string "VECTOR" in its entry code.

Refer to the sample version of the user exit DFSMSCE0's use of DFSMSCSVfor more information.
PFXUINVA 36/24 Upon return from the user exit IMS detected that the user prefix at MSCEUPR is invalid.

Possible causes are:

  • Length not in range of 5 to 512 bytes.
  • Address of prefix is invalid. Must be address obtained by IMS or within HIOP pool.
  • Length has been changed (MSCEBUPRL).
  • Address of user exit prefix has changed (MSCEBUPR).
  • Prefix code not 8E.

The programmer may need to turn on the DFSMSCE0 trace to trace the fields MSCEBUPR and MSCEBUPRL within the DFSMSCEB block.
PFXIINVA 37/25 Upon return from the user exit, IMS detected the Workload Router prefix at MSCEIPR is invalid.

Programmer response:

  • Length not in range of 5 to 512 bytes.
  • Address of prefix is invalid. Must be address obtained by IMS or within HIOP pool.
  • Length has been changed (MSCEBIPRL).
  • Address of workload router prefix has changed (MSCEBIPR).
  • Prefix code is not 8F.

The programmer may need to turn on the DFSMSCE0 trace to trace the fields MSCEBIPR and MSCEBIPRL within the DFSMSCEB block.
EXIOVLAY 38/26 User exit overlaid the 512 byte user work area buffer.

Programmer response: The user exit DFSMSCE0 appears to have overlaid the 512 byte workarea.

The overlay character string SCDSMCON is inserted at the end of the 512 byte workarea MSEBIBOV before calling the user exit DFSMSCE0 and is checked on return.

Refer to the user exit DFSMSCEB in the 6701-MSCE record to help determine the overlay.

EXBOVLAY 39/27 User exit overlaid the MSEB BCB block name (Overlay Check).

Programmer response: The user exit (DFSMSCE0) appears to have overlaid the DFSMSCEB block. The DFSBCB system service inserts a character string (MSEB) at the end of the DFSMSCEB block. IMS will abend when the DFSMSCEB block is returned by way of a DFSBCB release request. The DFS070 message will assist in determining when the overlay occurred.

Refer to the user exit parameter in the 6701-MSCE record to help determine the overlay.
EXPOVLAY 40/28 User exit overlaid the parameter list (Overlay Check).

Programmer response: The user exit DFSMSCE0 appears to have overlaid the user exit parameter list (DFSMSCEP). The overlay character string SCDSMCON is inserted at the end of the parameter list DFSMSCEP before calling the user exit DFSMSCE0 and is checked on return.

Refer to the user exit parameter in the 6701-MSCE record to help determine the overlay.

Codes 41 thru 52, shown in the following table, apply to the /FORMAT command.

Table 3. DFS070 reason (RSN) codes table for the /FORMAT command
Label Reason code decimal/hexadecimal Description
FMFND 41/29 The CNT for the terminal to be formatted was not found.
FMRCNT 42/2A The specified terminal is a remote LTERM.
FMDLNB 43/2B The specified terminal is a dynamic MSNAME (LNB).
FMMFST 44/2C The destination terminal (different from the input terminal) is not MFS-formatted.
FMLRESMD 45/2D The destination terminal is in line response mode.
FMTRESMD 46/2E The destination terminal is in terminal response mode.
FMCONV 47/2F Conversation is active on the destination terminal (when LTERM was specified in the command).
FMINP 48/30 The terminal is in input mode only.
FMEXCL 49/31 The terminal was in exclusive mode (when LTERM was specified in the command).
FMQBUF 50/32 The call to Queue Manager failed for a PUT LOCATE call.
FMIPREF 51/33 The INSERT PREFIX call to Queue Manager failed.
FMMSGNR 52/34 The call to enqueue the message failed.