Re: Same Record Key and FD for multiple VSAM files (of same structure)
- From: Robert <no@xxxxxx>
- Date: Sun, 23 Sep 2007 16:55:55 -0500
On Sun, 23 Sep 2007 18:30:03 GMT, "William M. Klein" <wmklein@xxxxxxxxxxxxxxxxx> wrote:
Robert,
I think you were missing the point that this is a "VSAM KSDS file" which seems
to indicate that this is an IBM mainframe application.
I was thinking AIX.
Although IBM now has a
way of changing the external file name dynamically, I don't think your
information is helpful for how to do this. (Move followed by OPEN is *not* the
way to do it).
Ok, it's done by changing an environment variable. Change MOVE to CALL 'putenv'. Same
idea.
Furthermore, your references to THREADs doesn't seem to know exactly what
threading is and is not supported by current IBM mainframes.
That's true. On AIX, you create a thread by calling pthread_create. It can be done 100%
in Cobol, no C required.
P.S. The qualification by FD-name is the simplest and most obvious solution for
what the OP wanted.
I wouldn't do it that way. If merging is required, I'd put OCCURS 5 on the record in
working-storage. Finding the lowest record out of 5,000 would then take no more code than
finding the lowest of 5 -- it would be a simple loop. Multiple qualified records will
produce copy-and-paste bloated code.
.
- Follow-Ups:
- References:
- Same Record Key and FD for multiple VSAM files (of same structure)
- From: dividby0
- Re: Same Record Key and FD for multiple VSAM files (of same structure)
- From: Robert
- Re: Same Record Key and FD for multiple VSAM files (of same structure)
- From: William M. Klein
- Same Record Key and FD for multiple VSAM files (of same structure)
- Prev by Date: Re: [OT] Iraq
- Next by Date: Re: [OT] Iraq
- Previous by thread: Re: Same Record Key and FD for multiple VSAM files (of same structure)
- Next by thread: Re: Same Record Key and FD for multiple VSAM files (of same structure)
- Index(es):