Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in


Differentiate through programs by PARM

Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IMS DB/DC
View previous topic :: :: View next topic  
Author Message

New User

Joined: 24 Mar 2005
Posts: 51

PostPosted: Sun Jun 05, 2005 6:05 pm    Post subject: Differentiate through programs by PARM
Reply with quote

Hi all,

In JCL, in PARM parameter i can pass different parameters.
May I know the meaning for all this.

My intention is By seeing this PARM parameter can I say whether this is an IMSBATCH or IMS-CICS or IMS-DC program.

Thanks in Advance.

Back to top
View user's profile Send private message


New User

Joined: 15 Aug 2005
Posts: 51

PostPosted: Tue Aug 16, 2005 2:17 pm    Post subject:
Reply with quote

IMSBACTH - will have either DL/I or BMP

IMSDC - will have MPP as the parameter
Back to top
View user's profile Send private message

New User

Joined: 23 Aug 2005
Posts: 4

PostPosted: Tue Aug 23, 2005 8:20 pm    Post subject: Differentiate through programs by PARM
Reply with quote

Please see below for more details


Specifies an application program name.

Restriction: The following description applies to batch procedures only.

Is an optional parameter specifying a PSB name when the PSB name and application program name are different.

The use of generated PSBs (GPSB) is supported in a TM batch environment. If the application program requires a GPSB, it must use the PSB parameter to indicate that request. In this case the PSB parameter does not specify the name of the PSB. Instead, it specifies a code that requests the use of a generated PSB and its language type. The specification of the code as the PSB parameter causes the specified GPSB to be utilized for the batch application program. The application program name (MBR parameter) is used as the GPSB name. GPSBs are not available in DB batch. The following coded character strings are used to identify the use of a GPSB and its language:

DFS$$ASM GPSB for the assembler language format.

DFS$$COB GPSB for the COBOL language format.

DFS$$PLI GPSB for the PL/I language format.

DFS$$PAS GPSB for the Pascal language format.

Restriction: The following definition applies to online procedures

Specifies the amount of subpool 231 storage to be allocated to the PSB pool. The value can be specified as one-to-six numeric characters or one-to-five numeric characters followed by K (kilobyte), M (megabyte), or G (gigabyte). If K, M, or G is not specified, K is the default. The maximum value that can be specified is 2G-1. If the value specified exceeds 2G-1 the default is 2G-1. The value specified is rounded up to the nearest page boundary.

The output of the ACBGEN utility indicates the maximum PSB size and the size of each PSB processed. This output should be examined before specifying the PSB= parameter.

For the FDR procedure, the sum of the values for the CSAPSB and DLIPSB defines the PSB pool size. If PSB is also specified, the larger value (PSB or the sum of CSAPSB and DLIPSB) is used.

Specifies an input transaction code. This parameter is necessary only when the application program intends to access the message queues. If this parameter is specified, the OUT= parameter is ignored. You cannot schedule a BMP with an IN= parameter specified against a PDIR with an associated SMB that is already scheduled. Doing so results in ABENDU0452 when the BMP is scheduled.
Specifies the transaction code or logical terminal name to which an output message is to be sent. This parameter is necessary when the application program wants to send output without accessing the input queues. A remote LTERM (CNT) cannot be specified.

This parameter is ignored if IN= is also specified.

Specifies what action to take when the message processing region starts, but when no system identifier matches the names given on IMSID or ALTID. The actions are:

W Wait for the control program to start.

N Ask operator for a decision. This is the default.

C Cancel message region automatically.

Specifies the SPIE option to:

0 Allow your SPIE, (the SPIE established by the application program), if any, to remain in effect while the application program call is being processed.

1 Negate your SPIE while the application program call is being processed. Negated SPIEs are reinstated before returning to the application program.

Under MVS, if SPIE=1, a SPIE must be established; otherwise, system abend ABEND46D is issued.

A value of 0 or 1 must appear in the generated JCL statement for this parameter.

Related Reading: For further information about IMS and SPIEs, refer to the topic, "How PL/I-IMS Error Handling Operates" in OS PL/I Version 2 Programming Guide, SC26-4307.

Specifies whether (1) or not (0) the addresses in your call list should be checked for validity. A value of 0 or 1 must appear in the generated JCL statement for this parameter. An address is invalid if it is either lower than the lowest address not in the MVS nucleus or higher than the highest address in virtual storage of the machine.
Specifies the size of the dependent region interregion communication area (DIRCA); the size specified must be a three-digit number (for example, 001) representing the number of 1-K blocks of subpool 251 to be reserved to hold a copy of your PCBs.

If you do not specify a DIRCA size, or if you specify a size of 000, IMS uses the system default for this message region. The size of the system default, determined during system initialization, is the maximum size required for any PSB. If necessary, IMS updates this default when an online change is made or when a dynamic PSB is scheduled.

Normally, you should not specify this parameter. You can use it to reduce the DIRCA size for a region where only PSBs with small DIRCA requirements are scheduled by class scheduling. The output from message DFS6891 occurring during ACBGEN facilitates DIRCA size calculation. Each PSB has a PCB=value that is the sum of the PCBs within it. The PCB value plus 64 is the required DIRCA size,
in bytes.

The Fast Path utility program uses a PSB that contains an I/O PCB and a DB PCB for the DBD specified in the JCL parameters. A DIRCA size of 002 is sufficient to contain the control blocks built for the PSB.

Specifies a two-character suffix for DFSMPLxx, the IMS.PROCLIB member identifying the modules to be preloaded in the region or partition. For more information, refer to "Member DFSMPLxx" in topic 7.2.8 and "Making High-Use Program Modules Resident" in topic

Restriction: The following description applies to batch systems only. Specifies whether (1) or not (0) the timer is to be set.

If STIMER=0 and a value is not entered for the CPUTIME= parameter, the time is not set. If STIMER=0 and a value is entered for the CPUTIME=parameter, the STIMER= parameter defaults to 1 and the timer is set. If nothing is entered for either the STIMER= or CPUTIME= parameters, the STIMER= parameter defaults to 0 and the timer is not set.

If STIMER=1, the timer is set and processor time statistics are gathered. The statistics include both application program time and DL/I processing time if the LSO=S option has been specified; most DL/I processing time is not included if LSO=Y is specified. One STIMER/TTIMER sequence is issued for each program invocation. STIMER=1 should only be specified for a BMP when gathering statistics. Specifying STIMER=1 for a BMP is similar to specifying STIMER=2 for an MPP.

Specifies the checkpoint at which the program is to be restarted.

Enclose the checkpoint ID in single quotes if it contains any non-ANSI characters, such as the slash.

Related Reading: See "XRST Call" in IMS Version 7 Application Programming: Database Manager, SC26-9422 for more information on specifying values for CKPTID.

You can suppress message DFS681I or DFS0540I each time a checkpoint call is made:

To suppress message DFS681I, code NOMSG681.

To suppress message DFS0540I, code NOMSG540.

To suppress both messages, code NOMSGS.

The values listed above (NOMSG681, NOMSG540, and NOMSGS) are not valid checkpoint restart IDs.

Specifies the parallel DL/I option.

0 DL/I processing is to be performed within the BMP region. This is the default.

1 All DL/I processing for this BMP is to be performed in the IMS control region.

PARDLI=1 prevents control region system 113 abends resulting from system X22 abends in the BMP region. If PARDLI=1, parallel DL/I is disabled. This can degrade performance.

Specifies the task timing option for either BMP or Fast Path.

0 No task timing is performed for this BMP or Fast Path region. A default value is placed in the 07 accounting log record to indicate that no timing was done. This is the default.

N A one- to four-digit number specifying the maximum task time in minutes to be allowed for the execution of this BMP or Fast Path region. The values can range from 1 to 1440 minutes. If a value of 1440 or greater is specified, a time of 24 hours is used. When N is nonzero, the STIMER=1 option is in effect.

For BMP task-timing, the measured time includes DL/I processing occurring in the dependent region. When the dependent region exceeds the specified time, a U0240 abend occurs after the current DL/I call completes. To control the execution time of a BMP, use CPUTIME=N instead of the TIME= of the operating system. If the operating system time limit is included with a job that specifies CPUTIME=N, ensure that the former is a sufficiently higher value to allow for initialization and one completed DL/I call beyond the CPUTIME value. When the CPUTIME=N option is used, the application program must not use the STIMER or TTIMER CANCEL.

For Fast Path programs, the timer is set at the beginning of program invocation. However, message-driven programs are not allowed to exceed the amount of time defined for the program to process a single transaction. In this case, CPRTIME=n is ignored.

A four-digit number specifying the number of Fast Path database buffers to be made available in the Common Service Area when the Fast Path region is activated. These buffers are used by the DEDBs to access VSAM control intervals, and by the MSDBs and DEDBs to hold information for updating between the DL/I call and synchronization point.

These buffers become part of the system database resources, but the number specified is reserved for exclusive use by this region when the application program accesses the MSDBs or DEDBs. (Although you are guaranteed access to a number of buffers, a maximum of the NBA + OBA value, you might have to wait for them.) The default is 0.

A four-digit number specifying the number of additional page-fixed buffers to be made available to a Fast Path application region if the normal allotment is used. In the Common Service Area, the system page fixes only enough additional buffers to handle the largest overflow specification from all active regions. The default is 0.

The system only allows one program at a time to use its overflow allocation. This is done to prevent a situation in which every program is waiting for buffers, when none is available. If an application needs more buffers than the sum of NBA + OBA, it abnormally terminates (for message-driven programs) or an FR status code is issued (for nonmessage-driven programs).

Specifies a one- to four-character identifier that is a valid subsystem identifier to the operating system being used. This identifier is used instead of the identifier specified at system definition of the IMS system being executed.

The IMSID name must not be the same as the procedure name that starts IMS unless one of the following is true:

All DD statements in the startup procedure are cataloged in the master catalog.

The unit and volume are specified on each DD statement.

This parameter cannot be changed at emergency restart. An IMSID name specified in the FDR procedure identifies the subsystem name for the FDR region.

Specifies the one- to eight-character application group name used for interregion communication security. The default is blanks.

Related Reading: For details on the use of the application group name, refer to the Security Maintenance utility information in IMS Version 7 Administration Guide: System, SC26-9420.

Specifies a one- to four-character identifier. When building IEBUPDTE JCL, you must generate the member name by concatenating this SSM identifier to the IMSID.

All external subsystems to be accessed by any region must be defined in this member. Essentially, the member specified by the IMS procedure is a master list. Dependent region procedures (DFSMPR, IMSBATCH, and IMSFP) can define subset lists. Each subset list can define all, some, or none of the external subsystems defined in the IMS master list. The SSM entry in each dependent region controls that region's access to subsystems.

Specifying SSM in a dependent region procedure but not in the IMS procedure is invalid, and no connection is made.

To allow a region to access all subsystems defined in the IMS procedure, do not code SSM. However, if preferred, the SSM entry can specify the same member as the IMS procedure.

To allow access to selected subsystems, specify a member defining only those subsystems a region is allowed to access. For example, if the IMS procedure member defines subsystems A, B, and C, but a region is only to access A and C, the region's SSM should specify a member defining only A and C. Thus, the SSM member is a subset of the IMS procedure member.

To prevent this region from accessing any subsystem, specify a member containing no entries.

Specifies a two-character suffix for DFSINTxx, the IMS.PROCLIB member that lists the preinitialization modules that are to receive control. For details on how to define the member, see "Tailoring the IMS System to Your Environment" in topic 7.0.

Specifies a one- to four-character name for an alternate IMS system. When your IMS message processing region tries to link to an IMS system, it tries to link to the system specified by the IMSID=parameter. If no IMS system matches the name specified with IMSID, the message processing region tries the system specified with the ALTID=parameter. If no IMS system matches the name specified with ALTID=, what happens next depends upon the option you choose on the OPT=parameter.

Specifies the 1 to 32-character parameter that is passed to the application program as part of the information returned in the INQY call with the ENVIRON subfunction. The parameter must be enclosed in single-quotes (') if special characters are used. Embedded commas (,) are not allowed.

Specifies a value between 1- and 32767- (in units of 1000). This parameter overrides the PSBGEN LOCKMAX value if one was specified. An override parameter of LOCKMAX=0 turns off all locking limitation.

LOCKMAX=10 Allows for 10000 locks.

LOCKMAX=0 Turns off locking limitation.
Back to top
View user's profile Send private message

New User

Joined: 11 May 2005
Posts: 20

PostPosted: Thu Aug 25, 2005 12:28 pm    Post subject: hi friends...
Reply with quote

Hi don't read the msg study.....

In most the applications ...we will use BMP,MPP because

the BMP is used for batch as well as online prog's,

for ex: the online job is running that produces some data that data we

have to use for batch applications.....that time it is use full and one more

thing is it won't affect any online applications that will keep on

running........Terminal response (user interaction ) is not require

MPP is used for pure online .......Terminal response is required.....
Back to top
View user's profile Send private message

New User

Joined: 11 May 2005
Posts: 20

PostPosted: Thu Aug 25, 2005 12:36 pm    Post subject: hi friends...
Reply with quote

To run the prog the minimum required parameters in PARM is


these parameters are enough.......

any doughts...come across................

If anybody want IMS material ...plz send a text mail to my -id..

Back to top
View user's profile Send private message

New User

Joined: 28 Jul 2005
Posts: 86
Location: Chennai

PostPosted: Tue Oct 11, 2005 10:27 am    Post subject: REGARDING IMS RUN JCL PARMS...
Reply with quote




Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IMS DB/DC All times are GMT + 6 Hours
Page 1 of 1


Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Can sending 5 MB data between cobol p... Kevin Vaz CICS 11 Tue Oct 18, 2016 4:50 pm
No new posts Using 'parm' to vary SORTOUT record v... Sysaron DFSORT/ICETOOL 13 Wed Sep 07, 2016 9:24 pm
No new posts User exit in COBOL programs ganasrinivasan PL/I & Assembler 0 Thu Aug 18, 2016 12:48 pm
No new posts "DFSRRC00 vs IKJEFT01" for ... arunsoods All Other Mainframe Topics 5 Fri Aug 12, 2016 9:54 pm
No new posts COBOL Programs Generator! Rohit Umarjikar COBOL Programming 1 Thu Jun 09, 2016 2:09 am

Back to Top
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us