Re: how to duplicate this mainframe process on iSeries?

Michael,

Typically, each member within a file has the same definition as all of the other
members.  I think I was assuming that the data submissions were all going to
have the same format.  Of course, you have have files with variable length
fields in them that would certainly qualify.

The OVERDBF MBR(*ALL) will consolidate all of the members into a single data
stream with the attributes associated with the *FILE object.  For example, if
you had multiple site submitting payroll data, it would all be coming in in the
same format (hopefully).  Each transmission would go into a separate member, but
at the end of the day you could read all of the members as if they were a single
file.

I'm not sure about the locking issue, maybe someone else will be able to address
that one.

Rich
  ------------------------------------------------------------------------

Michael Rosinger wrote:

Rick, Rich,

Now that sounds promising! But it raises some questions for me. Perhaps I am
not grasping the concept of multiple data file members in a single physical
file.

1) So a *FILE can have many members, each of which can contain thousands of
records of varying length? Amazing!

2) Using OVRDBF MBR(*ALL) would allow a COBOL program to read them all -
one-by-one?

3) Could this cause a potential locking problem for other processes that
need to create a new member while one of more file members may be being read
by another process?

--
Regards,

Michael Rosinger
Systems Programmer / DBA
Computer Credit, Inc.
640 West Fourth Street
Winston-Salem, NC  27101
336-761-1524
m rosinger at cciws dot com
<Rick.Chevalier@xxxxxxxxxxxxxxx> wrote in message
news:mailman.119.1168283517.12056.midrange-l@xxxxxxxxxxxxxxx

Michael,

I would recommend a single file with multiple members.  For each data
gather create a new member in the physical file.  At the end of the day
when it's time to process the data you could use the OVRDBF command MBR
parameter to specify all members.  When the processing is done remove
the members.  The DSPFD command with *MBRLIST for type of information
and *OUTFILE for output type will provide a list of members you could
loop through.

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Rosinger
Sent: Monday, January 08, 2007 1:05 PM
To: midrange-l@xxxxxxxxxxxx
Subject: how to duplicate this mainframe process on iSeries?

List,

Here's another unusual process we have on our VSE mainframe
that will have to be duplicated on the iSeries. I am hopeful
that the iSeries can handle this in a much easier manner than
does VSE, but I am too new to the environment to know.

Here's the process on VSE....

During the day, depending on which customers' data has
arrived, it is processed and their data "staged" to a
sequential file in a specific VSAM catalog. Throughout the
day, more data files are generated. When it is time to begin
the nightly run, we have to "gather" these files together
(merge to a single dataset) and then purge the original
individual files. (the catalog is backed up before the process begins)

The way this process is currently handled is a COBOL program
reads the VSAM catalog, looking for datasets whose name
matches specific templates. This program generates JCL for a
second job where another COBOL program will process each of
the specific files passed in the list that the first program
prepares. There is only one input file defined in this
program. Before each input file open, an assembler routine is
called which overrides the "ASSIGN TO name" of the file
hardcoded in the ASSIGN clause of the program with one that
is passed to the program in the list. This way it opens and
processes each file dynamically according to the list for that day.

If the iSeries provides a way to concatenate files of a
similar format with names that match certain template(s) to a
single file, this will be a piece of cake. The constraints here are:

1) there will be one-to-many of these files for any given run
- but all in the same library
2) the files will be identified by one of several "strings"
in their physical names
3) it is possible there could be other files in the same
library but are irrelevant to this process (so #2 is very important)

How best to accomplish this on the iSeries?

--
Regards,

Michael Rosinger
Systems Programmer / DBA
Computer Credit, Inc.
640 West Fourth Street
Winston-Salem, NC  27101
336-761-1524
m rosinger at cciws dot com


--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list To post a message email:
MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,
please take a moment to review the archives at
http://archive.midrange.com/midrange-l.

Privileged and Confidential.  This e-mail, and any attachments there to,
is intended only for use by the addressee(s) named herein and may contain
privileged or confidential information.  If you have received this e-mail
in error, please notify me immediately by a return e-mail and delete this
e-mail.  You are hereby notified that any dissemination, distribution or
copying of this e-mail and/or any attachments thereto, is strictly
prohibited.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.