|
midrange.com
We're going back a while in time (and really stretching my memory) - but
---
a.) We used vsam managed sam for a number of batch style transaction
files --- ie - in a payroll stream - program a
creates a file (vsam sam) and passes it to 10 other downstream
programs. This was a variable length, occurs
depending on file on vsam. When converted, we maxed it out --- and
the "depending upon" variable tells us
how many "buckets" we really used. It ended up not causing us to
make many code changes.
b.) We took and had reformat / rebuild programs for every master file we
had in the place. Remember - this was in
the day of "nifty" ODBC connections, etc --- so we had unload
programs to go to create a sequential 9 track
tape, took the 9 track tape to a PC, created a sequential file which
was then copied to the AS400 using 5250
emulation connections.
c.) We also had vsam files which had multiple record formats buried in
the same VSAM file --- each record format
had a different record layout / record length - you end up on the
iSeries using a "record selector program" and
having a lot more physical files (one for each record type - fixed
length of course) and then one logical file which
sits over all all the physicals combined......
Dale Nieswiadomy
Livingston County Information & Technology Services
(585) 243-7113
dnieswiadomy@xxxxxxxxxxxxxxxxxxx
"Michael
Rosinger"
<mrosinger@cciws. To
com> cobol400-l@xxxxxxxxxxxx
Sent by: cc
cobol400-l-bounce
s@xxxxxxxxxxxx Subject
Re: [COBOL400-L] COBOL/ILE
questions
08/22/2006 02:31
PM
Please respond to
COBOL Programming
on the
iSeries/AS400
<cobol400-l@midra
nge.com>
<DNieswiadomy@xxxxxxxxxxxxxxxxxxx> wrote in message
news:mailman.523.1156270400.5750.cobol400-l@xxxxxxxxxxxxxxx
As I remember, batch programs were a piece of cake --- change select statements and a few other minor changes. One problem area we did run into was that in straight VSAM, we had variable length files - which were a big no-no to the iSeries --- so we had to change them to fixed length at maximum occurrence. Files and file
formats
were definitely more "fun" than the code.
Dale, You just hit a nerve. We have lots of VSAM, especially VSAM-managed SAM and they are almost all exclusively with variable length records! I have already tried FTP'ing one of our typical sequential files to the iSeries and I encountered the variable length record issue. So, if on VSE the file is defined as variable length, is it enough to change the file descriptor in the program to match the longest occurrence? Will it also require a reformat/rebuild of the file to have all fixed length records? -- 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 COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
