IEBCOMPR Error

[makdiver]

Hi,

I've coded this

//STEP0150 EXEC PGM=IEBCOMPR
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSNAME=V001.AUSZ.DEPOT,
// DISP=SHR
//SYSUT2 DD DSNAME=V002.AUSZ.DEPOT,
// DISP=SHR
//SYSIN DD *
COMPARE TYPORG=PO
/*

and got this Errormessage

STEP0150,5101,D,SYSUT1 ,READ ,WRNG.LEN.RECORD,0000381C000100,BSAM

Both member are defined like this

DSN=V001.AUSZ.DEPOT,
DISP=(NEW,CATLG,DELETE),
DCB=(PDCB,RECFM=FB,LRECL=500),
SPACE=(500,(600,50),RLSE),AVGREC=K

What can I do better ?

Thanks

Michael

[steve-myers]

The message is telling you there is a difference between the declared DCB attributes of the data set and the actual data in the data set. The most common reason for this problem is the program that was supposed to write data to the data set never wrote anything to the data set.

Another problem is by stating TYPORG=PO in the IEBCOMPR control statement you are claiming the data sets are partitioned data sets, but the definition you show seems to indicate the data sets are sequential data sets. Sequential data sets do not have a PDS directory, and the error message is just telling you IEBCOMPR is trying to read the directory when there is no directory to read.

IEBCOMPR is a very stupid program and is rarely used any more. The SUPERC program that is part of ISPF is far superior.

[makdiver]

Thanks for the fast reply !
I know that SuperC would be better - but I was looking for a routine which will work in a batch job. But I saw no example how to use SuperC.

[willy jensen]

SUPER works nicely in batch too, as a TSO batch command. Sample;

Code: Select all

//SUPERC   EXEC PGM=IKJEFT1B            
//SYSTSPRT DD SYSOUT=*                  
//OLDDD    DD DISP=SHR,DSN=XX.TEST.LIB1
//NEWDD    DD DISP=SHR,DSN=XX.TEST.LIB2
//OUTDD    DD SYSOUT=*                  
//SYSTSIN  DD  *                        
 ISRSUPC COVSUM NARROW ALLMEMS          
//SYSIN    DD  *                        
CMPCOLM 1:100  

There are lots of options, check the manual for details.

[steve-myers]

SUPERC runs just fine in batch, but finding documentation about how to do it is somewhat difficult. The ISPF interface is just doctoring things up so it runs in the ISPF environment and then uses ISPF browse to display the SYSPRINT data set after it runs.

In my opinion, as a result the online displays are not as useful as they could be had it been planned from the start to be exclusively ISPF.

There is documentation in this link, which I found using Google.

[makdiver]

Thanks to you all - that helps a lot !

Dif-tor heh smusma