Joined: 10 Oct 2003 Posts: 317 Topics: 50 Location: Germany
Posted: Tue May 08, 2007 12:36 am Post subject:
priyam,
check the reasoncode !
See attached explenation from the userguide.
Explanation: The supervisor, or the Supervisor Call (SVC) for the BLDL (build a directory entry list) macro, detected an error during the processing of a LINK(X), XCTL(X),
ATTACH(X), or LOAD macro with the EP (entry point) or EPLOC (EP location (address)) operand.
The reason code in register 15 identifies the error:
Reason Code (hex) Explanation
04 The system could not find the module, whose entry point is the value of the EP or EPLOC operand, in the indicated library (private library, job library, or link library). This situation
can occur when LSEARCH=YES is specified on the macro and the limited library search fails to locate the module.
08 An uncorrectable I/O error occurred when the BLDL control program routine attempted to search the directory of the library that contained the program whose entry point was
specified in the EP or EPLOC operand. This can occur if the specified library is an uninitialized partitioned data set (PDS).
An incorrect data extent block (DEB) has been detected by the BLDL control program. The DEB was built in other than protect key 0 through 7.
0C The supervisor attempted to search a library for the program that the EP or EPLOC operand specifies and found that the library data control block (DCB) is not open.
10 A program issued a LOAD macro with the explicit load option, but there is no DCB parameter. For explicit loads, the program must supply the DCB parameter with the macro
because the system searches for the module that the LOAD specifies only in the library that the DCB parameter specifies.
14 The system could not find the module, whose entry point is the value of an EP or EPLOC operand of a XCTL(X) macro, in the link pack area (LPA), which is where the module
must be when the module is requested by an SVC routine.
18 An SVC routine issued a XCTL(X) macro for a module. The system tried to search the link pack area directory to find the module, but the directory had not as yet been built.
1C The data control block (DCB), included as part of a LINK(X), LOAD, XCTL(X), or ATTACH(X) macro is incorrect.
Joined: 10 Oct 2003 Posts: 317 Topics: 50 Location: Germany
Posted: Tue May 08, 2007 12:47 am Post subject:
priyam,
in case the procedure PLIXCLG is the original, unmodified version, override sysin with PL1L, not with PLI, start coding PL1 at column 2, not at column 1.
Regards,
bauer
Code:
//STEP1 EXEC PLIXCLG
//PL1L.SYSIN DD *
HELLO:PROC OPTIONS(MAIN);
PUT SKIP LIST('HELLO WORLD!!');
END HELLO;
/*
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
Posted: Tue May 08, 2007 9:35 am Post subject:
Actually, as it is a Compile, Link and Go the load module goes to a temp library. looking at the code it looks ok but I would still check the output from the compile and then from the link. Actually, check the return codes from the JESMSGLG.
I just ran it and it gave 00 for all 3 steps.
And the source goes in at
Code:
//PLI.SYSIN DD *
unless modified. _________________ Utility and Program control cards are NOT, repeat NOT, JCL.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum