mainframegurukul.com

A single ICETOOL step with five COPY statements correlating to five input DD statements should work for you.

The usual methods: 1. Use IPOUPDTE to change a specific field in all the members. 2. Copy the PDS to a sequential dataset using IEBPTPCH. Reformat and make the changes using SORT and create an IEBUPDTE-ready output stream. Use IEBUPDTE to build a new PDS. 3. Write your own utility using ISPF Library...

Presuming that you've broken down the input record into two fields, name and age, and then prompted for the input age, let's say name_in, then it's just a simple equivalency comparison:

If name_in == name Then Say name"'s age is" age.

dbzTHEdinosauer wrote:MrSpock,
just had to make it easy for him, didn't you?

Sorry, I won't do it again!

There's no date format exactly as you require, so I'd convert the julian date to the date sorted format:

thedate = Date('S',julian_date,'J')

which will give you 20121026 which you can then parse and string together into your format.

You'll probably find what you need on the BMC website.

You'll need a program to cause the delay (written in-house or obtained elsewhere) that preferably won't consume any CPU cycles. Personally, I use a Unix step (BPXBATCH) and invoke the Unix "sleep" command, or I use one of a few in-house written utilities.

Read the section "Sending binary files from MVS in a MIME attachment" and follow the example provided EXACTLY.

MVS Mail Page.

I'm not sure how to answer this since you posted your question to the TSO, CLIST, and REXX forum. For quick batch updates of a PDS I usually try the IPOUPDTE utility first. If that won't work, you can try using IEBPTPCH to copy the PDS to a sequential dataset, make the changes to that dataset, then ...

Nothing special required. You can concatenate as many PDS's with the members specified for input as you want (within system limits and following the rules of concatenation). Any copy program will work.

I'll never really get this concept. When a panel is displayed, the only real commands that are supported are END RC=8 or ENTER RC=0, SPLIT, HELP, and, if it contains scrollable areas, the UP and DOWN commands. Since ISPF users are usually familiar with these, why change what they're used to doing? A...

//FINAL EXEC EXTPROC,DSNAME=TSSDN.DEMO.TEMP02,DEFGDG=TSSDN.GDBD.TEMP02
//STEP2.SYSIN DD *
blah,blah...
/*

What is the length of the string VAR.I? Is it possible that the dataset name contains blank spaces that need to be stripped or parsed out? Judging by the fact that the dataset name:

'JHA07T11.INTA.JCLLIB

seems to be missing the ending single quote makes me think that that might be the case.

Or, as I mentioned, and as is repeated in the REXX manuals, for a variable that contains a dataset name, it's:

INFO = LISTDSI("'"VAR.I"'")

or

INFO = LISTDSI( double-quote single-quote double-quote variable_name double-quote single-quote double-quote )