Re: [IDMSVENDOR-L] automating journal file concatenation

Discussion created by ca.portal.admin on Feb 12, 2010

I really like the SHARE.ORG program SPECGDGC, which processes GDGs in
desired order.

Just feed it the gdg base name and it copies all generations

//step exec program=specgdgc,parm=''

It is on share tape 18, well I think that is what it is called, tape

I have seen this used for many years at some large sites hence avoiding
writing journal concatenation rexx execs.
I have also heard, through the grapevine, a software supplier has program
of this type in planning.

Rob Klan/Cincinnati/IBM
Phone: 1-877-205-4871 (T/L: 349-2446)
VOIP Users 1-513-897-8148
ITN: 23492446

Chris Hoelscher <choelscher@HUMANA.COM>
02/12/2010 01:40 PM
Re: [IDMSVENDOR-L] automating journal file concatenation
Sent by:

key - we run an IDCAMS to determine the datasets created during the
business cycle (day or week depending upon how frequently we backup) -
sort by generation # (ascending) - throw the formatted DD cards into an
INCLUDE librate, and run an ICEGENER to concatenate into a daily backup

we then take the same output from IDCAMS, format into DELETE statements,
and run IDCAMS again to delete the just-rolled-up journal tapes

Chris Hoelscher
IDMS/DB2 Database Architect
Humana Inc

you only need to test the programs that you want to work correctly

""Rozeboom, Kay [DAS]"" <KAY.ROZEBOOM@IOWA.GOV>
02/12/2010 12:42 PM
[IDMSVENDOR-L] automating journal file concatenation
Sent by:
IDMS 3rd-party providers forum <IDMSVENDOR-L@LISTSERV.IUASSN.COM>

Before trying to reinvent the wheel, I thought I would ask how others have
accomplished this: I am looking for a way to automate the generation of
statements for a job to concatenate journal offload files for the
day. Our journal offload file DSN's contain the date and time of offload
as part of their names. So it is easy enough to create the DD statements
anually. (Just cut and paste the DSN's from TSO panel 3.4.) But we would
like automate the process.

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov

The information transmitted is intended only for the person or entity to
which it is addressed and may contain CONFIDENTIAL material. If you
receive this material/information in error, please contact the sender and
delete or destroy the material/information.
IDMS 3rd-party providers forum


Re: [IDMSVENDOR-L] automating journal file concatenation
"We use a program to call IDCAMS to get the information. It is a flexible tool allowing you to alter the dates required instead of only the current one. It also gives you the option to list, copy or copy and delete in the same run. Unfortunately, I am not permitted to share LMC code but essentially the methodology is:

1. Accept a parm from a file or EXEC parm with the high level GDG name you wanted listed, copied, and/or deleted after copying with an optional date and operator with current date and equal as the default.
2. Build a LISTCAT statement for the above and output to SYSIN for use by IDCAMS. Close the SYSIN file.
2. Call IDCAMS to build a SYSPRINT file (you can either use the exit facilities documented in the Access Method Services manual or simply call IDCAMS with a dummy parm).
3. Read the SYSPRINT file looking for the DSN info you want (if they don't want current you will have to look at creation date).
4. After getting the files, if they only wanted a list, you are done. But...
5. If they want a copy done, then dynamically allocate the selected files and copy to an output dataset.
6. If they also want the files deleted after copy, dynamically allocate and delete the files.

Another method we use is for transmitting journal data from IDMS to Oracle. We use a tracking file that lets us know the last generation sent to Oracle. If the current GDG number is not one more than the number in the tracking file (with exceptions for 1 being the next number after 9999 and other variants), then the program dynamically allocates and copies all the necessary generations to the output file before processing by the other replication software. It also checks the DSCB statistics of the files and if the total number of tracks exceeds a threshold, then the output is directed to tape instead of DASD.

I can share some other general tips or techniques about either of the above. You may contact me directly at But again, I can't give you the code.

Dan Miley
Lockheed Martin