HP3000-L Archives

January 1998, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ron Horner <[log in to unmask]>
Reply To:
Ron Horner <[log in to unmask]>
Date:
Wed, 28 Jan 1998 07:02:04 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (46 lines)
From: Ron Horner@ILGW  on 01/28/98 07:02 AM


To:   [log in to unmask]
cc:
Subject:  CI Macros

You can use the VESOFT program STREAMX to construct loops within JCL.
Commands can be execution prior to job submission to the system.  So that,
your JCL may have a simple loop, but what is submitted are the repeated
commands.

If you want more info, let me know.

Thanks!

>>Greg Stigers said
>>Is there a reasonable way to set up a kind of macro within a job stream?
>>I want to avoid cluttering up the system with command files that are
>>used in a single job stream.
>>
>>I have a job stream that builds a list of groups for a new account. Much
>>of this is pretty simple stuff, so that all I have to change is the job
>>card for the new account, and set a couple of variables for things such
>>as group name and volume set. But the NEWGROUP logic is all of a kind,
>>using !HPACCOUNT, !HPSTREAMEDBY, etc. If I could collapse these
>>recurring lines to a single macro, it would greatly simplify that part
>>of the job, shortening it, and I hope reduce the clutter.
>>
>>The best ideas I can come up with are to build the command file with
>>echoes as a temp file, or to create a rather large environment variable
>>that uses the other environment variables, and that seems to me an
>>inobvious solution.



Ron Horner

Systems Programmer

Stone Container Corporation

[log in to unmask]

(312) 580-2982

ATOM RSS1 RSS2