M. Riley writes:
<<
I'm new to the HP way of doing business.  I came from an IBM mainframe
shop.

What I would like to do is setup our job streams similar to the way we
did JCL

where I came from.  For example, to create a generation data set we
just said
'filename' +1.

This automatically created the next data set.  How do we do this in
the HP
world?

>>

Mr. Riley,
    It has been many years since I wrote for the IBM mainframes, but I
remember
data generation sets very well. It provided a very succinct but
limited form of maintaining
successive generations of disc files for reference. On the HP3000 this
technique is very
simple to emulate. For example it can be done in JCL such as:

WHILE FINFO("ABC!SETNUM.GROUP.ACCOUNT","EXISTS") DO
   SETVAR SETNUM = SETNUM + 1
ENDWHILE
BUILD ABC!SETNUM.GROUP.ACCOUNT;REC=-256,16,F,ASCII;DISC=1024,1,1
<< REMAINING JCL WHICH REFERENCES ABC!SETNUM.GROUP.ACCOUNT >>

or in a dynamic program(references resolved at execution time) that a
calling program can
activate as it executes. With simple logic and a few calls to specific
HP3000 INTRINSICs the status of these already existing files can be
queried for ANY additional information
affecting decision making. This is just a small sample of what can be
accomplished on
every HP3000. Please use this listserv as often as possible, there are
many of us that will
attempt to answer your questions.

                                           Eric Sand
                                           Data Research Associates
                                           [log in to unmask]