Parm values are not correctly passed to the executing pgm.

Rajesh S · New User Joined: 11 Jul 2007 Posts: 54 Location: Chennai

Dear All,

I am passing some values to the executing program thru PARM parameter. These values are not correctly passed to the program.

Below is the EXEC statement in JOB.
//STEP1 EXEC PGM=PROG1,PARM=2120104XX,REGION=4096K

Below the Linkage section field decalaration.
LINKAGE SECTION.
01 PARMAREA.
05 PRM-LENGTH PIC S9(4) COMP.
05 PRM-DATE.
10 PRM-DATE-1 PIC X(1).
10 PRM-DATE-YY PIC X(2).
10 PRM-DATE-MM PIC X(2).
10 PRM-DATE-DD PIC X(2).
05 PRM-FREQ PIC X(1).
05 PRM-REPORT-IND PIC X(1).

Below is the abend getting during the execution.

IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=0C4 REASON CODE=00000004
TIME=02.25.14 SEQ=36492 CPU=0000 ASID=016F
PSW AT TIME OF ERROR 078D0000 9FD02BEE ILC 6 INTC 04
ACTIVE LOAD MODULE ADDRESS=1FD02BE8 OFFSET=00000006
NAME=DSNALI
DATA AT PSW 1FD02BE8 - D3C9C3C5 D5E2C5C4 40D4C1E3
GR 0: 1FD010CC 1: 1FD010A0
2: 00000000 3: 00007000
4: 0098B000 5: 00988398
6: 7F4FB4D0 7: 7F4FB4D0
8: 1AA34C98 9: 00BE4008
A: 1FD01000 B: 00007000
C: 1AA26D10 D: 1FD01250
E: 9AA26DAE F: 1FD02BE8
END OF SYMPTOM DUMP
IEF472I F36981CT S1CP01 - COMPLETION CODE - SYSTEM=0C4 USER=0000 REASON=00000004

Please let me know, your valuable comments to resolve the issue.

Thanks in Advance.

Thanks!
Rajesh S.

chandan.inst · Posted: Wed Jan 18, 2012 10:16 am

Hi Rajesh,

By looking to the dump, it doesnt look like the error is becuase PARM values are not getting passed correctly

Can you please provide cod ein your program?

Regards,
Chandan

Bill O'Boyle · Posted: Wed Jan 18, 2012 10:18 am

In the JCL, the parm value needs to be enclosed in quotes as '2120104XX'.

To ensure the program has received the proper parm-length, check that PRM-LENGTH is not less than LENGTH OF PRM-DATE.

Also, PRM-FREQ and PRM-REPORT-IND must be defined as level 10 and NOT as level 05 as they are elementary items of group PRM-DATE.

Mr. Bill

chandan.inst · Posted: Wed Jan 18, 2012 10:26 am

Thanks Bill..

Missed the linkage section code in my earlier post..

-Chandan

Rajesh S · New User Joined: 11 Jul 2007 Posts: 54 Location: Chennai

Hi Bill,

Thanks for your response.

I have ensured the parm-length in both program as well as in JCL, both are same only.

I hope, level numbers might not be an issue. Because in production, it works as expected. Issue is raising in test region alone.

Thanks!
Rajesh S.

Bill Woodger · Posted: Wed Jan 18, 2012 12:44 pm

Can you, from your compile listing, show the PROCEDURE DIVISION USING, please?

Rajesh S · New User Joined: 11 Jul 2007 Posts: 54 Location: Chennai

Hi Bill,

Please find the below Compiler listing and procedure division declaration.

Compiler Options in effect:
NOADATA
NOADV
APOST
ARITH(COMPAT)
AWO
BUFSIZE(28672)
NOCICS
CODEPAGE(1140)
NOCOMPILE(E)
NOCURRENCY
DATA(31)
NODATEPROC
NODBCS
NODECK
NODIAGTRUNC
NODLL
NODUMP
DYNAM
NOEXIT
NOEXPORTALL
NOFASTSRT
FLAG(I,E)
NOFLAGSTD
INTDATE(ANSI)
LANGUAGE(EN)
LIB
LINECOUNT(60)
LIST
MAP
NOMDECK
NONAME
NSYMBOL(DBCS)
NONUMBER
NUMPROC(MIG)
OBJECT
NOOFFSET
OPTIMIZE(STD)
OUTDD(SYSOUT)
PGMNAME(COMPAT)
RENT
RMODE(AUTO)
NOSEQUENCE
SIZE(MAX)
SOURCE
SPACE(1)
NOSQL
NOSQLCCSID
NOSSRANGE
TERM
TEST(NONE,SYM,SEPARATE)
NOTHREAD
TRUNC(OPT)
NOVBREF
NOWORD
XREF(FULL)
YEARWINDOW(1900)
ZWB

Procedure division declare as below:

PROCEDURE DIVISION USING PARMAREA.

Bill Woodger · Posted: Wed Jan 18, 2012 2:06 pm

Why do you think the PARM is the problem?

If you look at the dump, the offset is 6! The program is DSNALI, and the PSW, which should be pointing to some code, contains the value "LICENSED MAT".

Are you using DB2? Can you show us the JCL that executes the program?

enrico-sorichetti · Posted: Wed Jan 18, 2012 2:06 pm

there is no evidence that the parameter passing is wrong.
to get that evidence You should at program startup jus print/display the parm length and the parm value
simple snippet...

Bill Woodger · Posted: Wed Jan 18, 2012 2:36 pm

enrico, I like the formatting of the divisions/sections.

Just a couple of extra thoughts.

PeterHolland · Posted: Wed Jan 18, 2012 2:42 pm

Rajesh S,

there you are. A very nice solution of Bill Woodger.

Rajesh S · New User Joined: 11 Jul 2007 Posts: 54 Location: Chennai

Program not using DB2, but some called program will use. I did the Xped and confirm that, PARM values are having SPACES/JUNK values..

Now am checking with some other programs, That also abend with same reason. I have compiled my programs using CHANGEMAN.

I couldnt find the module DSNALI in any load libraries.

Thanks in advance.

enrico-sorichetti · Posted: Wed Jan 18, 2012 2:54 pm

we are just wasting time
nothing You posted makes any sense
if the <parms> passed are <wrong> start with the snippets we posted to find out why

dir you tell the truth when You said

Rajesh S · New User Joined: 11 Jul 2007 Posts: 54 Location: Chennai

Issue got resolved after include the load module of DSNALI from the library dataset as below.

//JOBLIB DD DSN=E2022TDA.DB2TEST.DSNLOAD(DSNALI),DISP=SHR

lindovaldolpn · New User Joined: 25 Feb 2010 Posts: 16 Location: Brazil

Problably your program does call another assembler/db2 program. And this program abended.
Whey you run a db2 program you need execute using IKJEFT01 or compile your program including CAF modules. The second way is rarely.

You can use...
//STEP01 EXEC GM=IKJEFT01,DYNAMNBR=20
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DSN?)
RUN PROGRAM(PROG1) PLAN(PROG1??) PARM('2120104XX') -
LIB('your.loadlib')
END
//* Your JCL complement

Regards
Lindovaldo