Page 1 of 2

merge multiple seq files onto one

PostPosted: Thu Feb 16, 2012 6:23 am
by dn2012
Hello All,
Source: SYSMC.TTT.AGNCYIMF.DATA

Under this I have following member/files.

SYSMC.TTT.AGNCYIMF.DATA.G1
SYSMC.TTT.AGNCYIMF.DATA.G2
SYSMC.TTT.AGNCYIMF.DATA.G3
SYSMC.TTT.AGNCYIMF.DATA.G4
SYSMC.TTT.AGNCYIMF.DATA.G5

My goal is to move these files onto another PDS and run the JCL for billing transaction.
Destination PDS.DESTIN.IMF310/ITD.SOURCE.

I created member called T021512 in the
How should I move all sequential files onto one PDS.DESTIN.IMF310/ITD.SOURCE.T021512

thx

Re: merge multiple seq files onto one

PostPosted: Thu Feb 16, 2012 6:36 am
by steve-myers
  • Review the documentation for the preferred copy utility at your site. If there is none, review the documentation for IEBGENER.
  • Review the documentation about dataset concatenation in the JCL Reference manual for your z/OS release.
  • If you are unable to perform the preceding tasks, hire a consultant.

Re: merge multiple seq files onto one

PostPosted: Fri Feb 17, 2012 2:22 am
by dn2012
I fixed it as below: (Do not need consultant ) :- )

SYSMC.TTT.AGNCYIMF.DATA.G1

//STEP010 EXEC PGM=IEBGENER
//SYSUT1 DD DSN=SYSMC.TTT.AGNCYIMF.DATA.G1,DISP=SHR
// DD DSN=SYSMC.TTT.AGNCYIMF.DATA.G2,DISP=SHR
// DD DSN=SYSMC.TTT.AGNCYIMF.DATA.G3,DISP=SHR
// DD DSN=SYSMC.TTT.AGNCYIMF.DATA.G4,DISP=SHR
// DD DSN=SYSMC.TTT.AGNCYIMF.DATA.G5,DISP=SHR
//SYSUT2 DD DSN=IMSTESTA.IMF310.ITD.SOURCE(T021512 ),DISP=SHR
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//*
******************************** Bottom of Data ************************************

Re: merge multiple seq files onto one

PostPosted: Fri Feb 17, 2012 3:13 am
by BillyBoyo
I'd put DISP=OLD on the SYSUT2. PDSs can get pickled by more than one thing updating at once. With "OLD" you have no danger of someone else (or yourself) updating at the same time.

Re: merge multiple seq files onto one

PostPosted: Fri Feb 17, 2012 3:50 am
by dn2012
Thanks

You think it can also load duplicate values.

Re: merge multiple seq files onto one

PostPosted: Fri Feb 17, 2012 4:12 am
by dn2012
i CHAGED TO OLD BUT DID NOT WORK.
I PUT BACK DISP=SHR

BUT NOW GETTING MESSAGE AS:
14.40.42 JOB14951 $HASP165 DNMEMB ENDED AT LACMAS - ABENDED SE37 U0000 CN(INT
ERNAL)

Re: merge multiple seq files onto one

PostPosted: Fri Feb 17, 2012 4:26 am
by enrico-sorichetti
and... what happened when You looked at the messages manual and at the systems codes manual ?

Re: merge multiple seq files onto one

PostPosted: Fri Feb 17, 2012 4:35 am
by BillyBoyo
A member of a PDS is just a sequential file. You can have as many duplicates as you want.

In what way did DISP=OLD not work?

You need to learn how to look up messages, abend codes and things like that. Even if you google for Abend SE37 you'll find the information you need.

If you are putting lots of data into a member, and it is a PDS not a PDSE, you will get quite regular space problems. If you don't know anything about compressing a PDS, including making a back-up of it first, then get in touch with someone at your site who does, and seek their assistance. In a PDS, when a member is created, the space previously referenced by that member is just abandoned, to be recovered later by a compress. PDSEs recover the previously used space as they go along.

Maybe while doing your testing with bulk data, just use a plain sequential file, not a member.

Re: merge multiple seq files onto one

PostPosted: Fri Feb 17, 2012 4:39 am
by steve-myers
dn2012 wrote:... BUT NOW GETTING MESSAGE AS:
14.40.42 JOB14951 $HASP165 DNMEMB ENDED AT LACMAS - ABENDED SE37 U0000 CN(INT
ERNAL)

You also got an IEC032I message. You will find this message useful in your problem determination.

Re: merge multiple seq files onto one

PostPosted: Fri Feb 17, 2012 4:47 am
by dn2012
I TRIED THIS BUT STILL GETTING SAME MESSAGE

Step 1: Start
Step 2: 3.4
Step 3: Provide the name of PDS
Step 4: Press ENTER
Step 5: Enter "Z" against the PDS
Step 6: Press ENTER