Strange Problem: System Code S106



Hello IBMMAIN List,

we faced a strange problem with a system code S106,
as response to a LOAD macro call.

Although the LOAD was not successful (I/O error on the PDS),
the LOAD in error added an entry into the CDE with the
requested module's name, and an entry point address X'80000000'.

This seems to be normal behaviour; the entry is made before the
actual processing of the PDS member. Even the AMODE is already
known to be 31 (from the dictionary), so the entry get's the
address X'80000000'.

The S106 error is captured by our own error processing, a message is
produced (including alert mail), and processing continues (IMS region).

Later on, the same module is to be fetched again. We do this
by lookup of the CDE, and now the problem is: we find an entry
in the CDE, get the address from there (which is X'80000000')
and try to call the module at this address, which, of course,
leads to another error, in this case S0C1.

My question is:

what do you think about the strange CDE entry? Shouldn't it be
removed, following the S106?

Kind regards

Bernd

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

.



Relevant Pages

  • Re: Strange Problem: System Code S106
    ... we faced a strange problem with a system code S106, as response to a LOAD macro call. ... Although the LOAD was not successful, the LOAD in error added an entry into the CDE with the requested module's name, and an entry point address X'80000000'. ...
    (bit.listserv.ibm-main)
  • Re: Strange Problem: System Code S106
    ... there should never be an I/O error on the load library PDS. ... I guess, that the entry is inserted in CDE, when the directory entry ...
    (bit.listserv.ibm-main)
  • Re: Concatenation order in STEPLIB
    ... When you load a module, the system must first find its directory entry. ... the first data set in the concatenation in which that module lives). ... The LNKLST, when LLA is managing the entire LNKLST, is an exception, as LLA ...
    (bit.listserv.ibm-main)
  • RE: PGM= and alias CDE
    ... entry point an additional entry point in my main program. ... be better off making BBB the primary name and making AAA an alias, ... Q.If AAA is the jobstep program and AAA has an alias of BBB, then is a CDE ...
    (bit.listserv.ibm-main)
  • Re: IDENTIFY questions
    ... When IDENTIFY creates a minor CDE, ... "If an authorized caller creates an entry name for a module in the link ... pack area queue. ...
    (bit.listserv.ibm-main)