|
View previous topic :: View next topic
|
| Author |
Message |
mahi
New User
.jpg)
Joined: 04 Apr 2006
Posts: 86
Location: Hyderabad
|
|
|
|
| Code: |
//A12345 EXEC PGM=IKJEFT1A,
// DYNAMNBR=30,
//STEPLIB DD DSN=DB2B.REF.LDCLOAD,
// DISP=SHR
// DD DSN=DB26.REF.LDCEXIT,
// DISP=SHR
// DD DSN=SYS2.LDCS.PRODLOAD,
// DISP=SHR
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DSN=SYS2.OPER.PARMLIB(A12345P),
// DISP=SHR
//PRODPARM DD DSN=SYS2.OPER.PARMLIB(A12345S),
// DISP=SHR
//DISK DD DSN=P.A12345.LDCS01.C&DATE01.01,
// DISP=SHR
//SYSOUT DD SYSOUT=*
|
Here I'm executing the cobol-db2 program which is in parm parameter a12345p.
From PRODPARM I am supplying some data to the cobol-db2 progarm. So how can I capture the PRODPARM values in the cobol-db2 program. I need to have this variables in an internal cobol table.
Structure of A12345S:
LDC ID 4 byttes
LDC OPT CLSS 2
OPT ID 4
eX: LDC1 NA 0000
LDC2 NA 9999
LDC3 EX 0000 |
|
| Back to top |
|
 |
rpuhlman
New User
Joined: 11 Jun 2007
Posts: 80
Location: Columbus, Ohio
|
|
|
|
Mahi,
You would treat PRODPARM as any other input file in your program. Assuming (yuk) PRODPARM is the name of the file in your SELECT statement in FILE-CONTROL you would OPEN INPUT PRODPARM , READ PRODPARM, Move your variables, CLOSE PRODPARM ... Simplistic example, but you should get the idea.
Rick |
|
| Back to top |
|
|
mahi
New User
Joined: 04 Apr 2006
Posts: 86
Location: Hyderabad
|
|
|
|
Thanx rick..
Can we open the PRODPARM as any other file??IF that is the case my problem will be solved...
Am asking again just for confirmation... |
|
| Back to top |
|
|
rpuhlman
New User
Joined: 11 Jun 2007
Posts: 80
Location: Columbus, Ohio
|
|
|
|
Hi Mahi,
Yes.
Rick |
|
| Back to top |
|
|
|
|
