sundarkudos
New User
Joined: 16 Oct 2008
Posts: 39
Location: Chennai
|
|
|
|
Hi All,
When I compile a PL/I DB2 program on a Z/OS v1.13 machine running with DB2 V8.1 and Enterprise PL/I v4.2, below warnings are encountered during Bind process. REXX screen which is linked this PL/I DB2 component started failing due to this.
The same program was then compiled with PL/I v1.1 and DB2 v8.1 setup, which did not throw* any of these warnings and the REXX screen also working fine. For some reason, the link step is added with DSNHLI, DSNELI and DSNALI to the load module and which in turn mess up the setup done for PL/I v4.2. Has anyone ever seen this behavior before?? Please guide me to resolve this issue.
* Nothing would 'throw' anything as ;throw' is not a mainframe term (moderator)
| Code: |
IEW2480W A711 EXTERNAL SYMBOL DSNHLI OF TYPE LD WAS ALREADY DEFINED AS A SYMBOL OF TYPE LD IN SECTION DSNELI.
IEW2482W A712 THE ORIGINAL DEFINITION WAS IN A MODULE IDENTIFIED BY DDNAME SYSLIB. THE DUPLICATE DEFINITION IS IN
SECTION DSNALI IN A MODULE IDENTIFIED BY DDNAME SYSLIB.
IEW2480W A711 EXTERNAL SYMBOL DSNWLI OF TYPE LD WAS ALREADY DEFINED AS A SYMBOL OF TYPE LD IN SECTION DSNELI.
IEW2482W A712 THE ORIGINAL DEFINITION WAS IN A MODULE IDENTIFIED BY DDNAME SYSLIB. THE DUPLICATE DEFINITION IS IN
SECTION DSNALI IN A MODULE IDENTIFIED BY DDNAME SYSLIB. |
and, the module map is below
| Code: |
E478 DSNELI * CSECT 296 SYSLIB 08 DSNHLI
E494 DSNWLI LABEL
E4A4 DSNHLI LABEL
FD28 DSNALI * CSECT 310 SYSLIB 08 DSNALI
FD42 DSNASP LABEL
FD48 DSNHLI2 LABEL
FD54 DSNWLI2 LABEL |
Error screenshot is below::
| Code: |
**************************************************
*** SQL ERROR ENCOUNTERED AT 17.22
*** ON 09/05/16
*** PROGRAM ==> SGPI01R
*** SQLCODE ==> -927
*** FUNCTION ==> PREPARE BATCH_SQL FROM :SQL_STMT
*** TABLE NAME ==>
***-----------------------------------------------
*** ERROR MESSAGE : -
*** SQLCODE = -927, ERROR: THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN
*** THE CONNECTING ENVIRONMENT WAS NOT ESTABLISHED. THE PROGRAM SHOULD B
*** INVOKED UNDER THE DSN COMMAND
***
*** SQLSTATE = 51006 SQLSTATE RETURN CODE
*** SQLERRP = DSNELI SQL PROCEDURE DETECTING ERROR
***
***
************************************************** IDI0055E Fault Analyzer processing excluded because 4 meg of 31 bit storage is not currently available
IDI0087I 11.8 Meg of 31 bit storage could be provided by SETPROG LPA,ADD,MOD=(I
DIDA),DSN=LNKLST
IDI0126I Recovery fault recording fault ID F87207 assigned in history file SYSU
.IFA.AAQ3.HIST
IGD01008I SYSU.IFA.GDP3.D160509.T072201.SSU24: IS SMS MANAGED BY DEFAULT
IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO SYSU.IFA.GDP3.D160509.T072201.SSU2
4
IEA995I SYMPTOM DUMP OUTPUT
USER COMPLETION CODE=3000
TIME=17.22.01 SEQ=02240 CPU=0000 ASID=0121
PSW AT TIME OF ERROR 078D1E00 802BAB2A ILC 2 INTC 0D
ACTIVE LOAD MODULE ADDRESS=002BAA88 OFFSET=000000A2
NAME=VABENDL
DATA AT PSW 002BAB24 - 00181610 0A0D5820 60041222
GR 0: 80000000 1: 80000BB8
2: 002BAAEE 3: 260B5604
4: 260BBAE0 5: 00000000
6: A60C72F8 7: 002CC6EC
8: 000000A8 9: 002CB438
A: 002BAA88 B: 0000000E
C: 0028CBD8 D: 002CF360
E: 802BAB12 F: 002BADD0
END OF SYMPTOM DUMP
IRX0250E System abend code 0C4, reason code 00000017.
IRX0255E Abend in host command SETMSG or address environment routine ISPEXEC. |
Thanks,
Sundar
Coded - you should be able to do this by yourself after all these years |
|
