Would my PARMCNTL help?

>From CBT
//*+File 839:  Long Parameters in EXEC - JCL symbolic substitution  *   DOC
FILE

It takes a parameter and copies it to a Card file (or a VB Data Set).   It
fills in Symbolic Parameters from the Parm Field, and can accept long
parameters.

It also has the ability to split the card image file by coding <P> at
various points.

It can also optionally execute a program after it has created the card
image file.

Here is an example.  It calls IEBCOPY after creating a card image file
from the parameters.
==============

//PDSCOPYM PROC  INDSN=,OUTDSN=,MEM=
//*
//* This procedure copies members from one PDS to another
//* and selects the specified members.
//*
//* For example,
//*  // EXEC PDSCOPYM,INDSN=SYS1.PROCLIB,
//*  //      OUTDSN=SYS2.PROCLIB,
//*  //      SELECT=RDR,MEMBER2
//*
//* This JCL Executes IEBCOPY with the SELECT option.
//* It is similar to the Jol Copy command (see Jol).
//*
//* Note: Program PARMCNTL below executes the PGM in the Parm
//* field after creating control statements on the DDN Ddname
//* AFTER the Symbolic &SELECT has been filled in.
//*
//* The <P> is the equivalent of a Newline character. Thus new
//* CONTROL CARDS CAN BE CREATED.
//*
//COPYMEM  EXEC PGM=PARMCNTL,REGION=4096K,
// PARM=('PGM=IEBCOPY,DDN=SYSIN',
//       ' C I=INFILE,O=OUTFILE<P> S M=&MEM')
//SYSIN    DD  DCB=(RECFM=FB,LRECL=80,BLKSIZE=800),   Created by Prog.
//         UNIT=VIO,SPACE=(TRK,10)
//SYSPRINT DD  SYSOUT=*
//INFILE   DD  DSN=&INDSN,DISP=SHR
//OUTFILE  DD  DSN=&OUTDSN,DISP=OLD

.

On Mon, May 19, 2025 at 11:27 PM Paul Gilmartin <
0000042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:

> On Mon, 19 May 2025 10:16:02 +0000, Seymour J Metz wrote:
>
> >There is nothing in JCL for calling a program with multiple parameters.
> Even in TSO the CPPL points to a single parameter string, from which the
> program normally relies on parse services to extract positional and keyword
> parameters. only in Unix does the program receive multiple parameters.
> >
> JCL and CPPL, yes, but aren't you familiar with the CALL, LINK, ATTCH,
> and XCTL macros?  Do you consider it likewise "Too bad they didn't do
> something similar for":
> o The first parameter?
> o Every parameter?
>
> >It's prudent to validate parameters, but hardly customary. Sturgeon's Law
> applies. The code that I've seen ranges from ghastly to excellent, with
> most somewhere in between, and I can't think of any rule of best practice
> that doesn't get violated.
> >
> >________________________________________
>
> >On Mon, 19 May 2025 02:36:47 +0000, Seymour J Metz wrote:
> >
> >>Yes, which is why IM  provided for controlling long parameters for
> authorized programs. Too bad they didn't do something similar for AC(0).
>
> --
> gil
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to