JCL - COBOL IMS - Parm issue

vinu78 · Active User Joined: 02 Oct 2008 Posts: 179 Location: India

Hi,

I want to execute the IMS Batch program wherein I need to pass 'TRAN' through JCL that is used inside the IMS-COBOL program. The problem is that when calling IMS COBOL pgm through JCL, we need to pass module name also in PARM and my needed parm 'TRAN' is not correctly passed to COBOL.

vinu78 · Active User Joined: 02 Oct 2008 Posts: 179 Location: India

Hi all,

Could anyone of you please help me in resolving the Parm issue mentioned above ?

Thanks
Vinu

dick scherrer · Posted: Tue Jun 29, 2010 12:37 am

Hello,

Maybe you should consider using a SYSIN DD for this data rather than a PARM. . .?

Unfortunately i don't "do" ims and don't know how this might be done with an ims program. . .

CICS Guy · Posted: Tue Jun 29, 2010 12:38 am

PARM=subparameter
PARM=(subparameter,subparameter)
PARM=('subparameter',subparameter)
PARM='subparameter,subparameter'

dick scherrer · Posted: Tue Jun 29, 2010 12:45 am

Hello,

I believe ims intercepts the parm and it is not given to the linkage section field(s).

CICS Guy · Posted: Tue Jun 29, 2010 1:36 am

Procedure Division using IO-PCB DB-PCB-Mast DB-PCB-Detail.
...
Figure 7. Sample COBOL program
...
Notes to Figure 7:
...
This is the standard procedure division statement of a batch program. After IMS has loaded the PSB for the program, IMS passes control to the application program. The PSB contains all the PCBs that are defined in the PSB. The coding of USING on the procedure division statement references each of the PCBs by the names that the program has used to define the PCB masks in the linkage section. The PCBs must be listed in the order in which they are defined in the PSB. ?
So the parms passed to DFSRRC00 are not the parms expected by the application program?

dick scherrer · Posted: Tue Jun 29, 2010 2:20 am

Hi Guy,

vinu78 · Active User Joined: 02 Oct 2008 Posts: 179 Location: India

Yes D.sch.
My question is whether we can pass additional 4 bytes in addition to IMS parmlibs

We don't need to explicitely tell the PROCEDURE DIVISION USING when we are passing only IMS parmlibs. However if we need to pass data (nt related to IMS), we need to specify and it is not allowing me to do so.

I will do some trial and error and if I get the result, will let the group know abt it.

Thanks
Vinu

PeterHolland · Posted: Tue Jun 29, 2010 12:20 pm

The following is maybe usefull :

Use the APARM= parameter to specify execution-time parameters unique to this dependent region. This parameter specifies a character string for the application program or Data Capture exit routine. For batch or BMP regions, the APARM= can used to pass parameters to the Data Capture exit routine to indicate whether the data should be captured.
The maximum length of the parameter is 32 characters; the parameter must be enclosed in single quotes (') if special characters are used; embedded commas are not allowed. The INQY call with the ENVIRON subfunction is used to receive the APARM character string.

Parameters for IMSBATCH (DFSRRC00) are described in :

IMS Installation Volume 2: System Definition and Tailoring GC18-7823-03

vinu78 · Active User Joined: 02 Oct 2008 Posts: 179 Location: India

Hi Peter,

Could you please pass me the sysntax of APARM and how to put it along with the existing JCL card.

dick scherrer · Posted: Tue Jun 29, 2010 8:53 pm

Hello,

Did you read the referenced material from the manual (rather than chasing thru Google)?

Did you look within this forum? This topic was posted previously:

vinu78 · Active User Joined: 02 Oct 2008 Posts: 179 Location: India

Hi D Sh,

Thanks for the pointer.
I saw that topic in this forum yesterday however didn't get any clear idea about APARM. I will try the APARM else go with the SYSIN logic mentioned by you.

Thanks
Vinu

dick scherrer · Posted: Wed Jun 30, 2010 2:01 am

Good luck - one way or another it will soon work

d