BXEnter?? - in VSAM file processing

avelayudhan · New User Joined: 30 Nov 2005 Posts: 26

I am getting a mysterious 'error' while processing a KSDS VSAM file. Initially, the file's top few rows are

-NOTE- CAPS MODE IS "ON"
H***H01 000 ::PAYMENT HISTORY REPORT FOR HRP
H***H01 001 //GSSXXXX JOB XXXXX,'GENESYS OLPHRPTH',PRTY=12,
H***H01 002 // REGION=5100K,CLASS=A
H***H01 003 // JCLLIB ORDER=GENESYS.PROCLIB
H***H01 004 //JOBLIB DD DSN=GENESYS.LOADLIB,DISP=SHR
H***H01 006 //* DD DSN=SYS1.CEE.V1R5M0.SCEERUN,DISP=SHR
H***H01 007 //OLPHRPTH EXEC OLPHRPTH

Then while accessing the program that uses this VSAM, a record is added at the top of the file by the OS? Anyone know what this record is and why this been inserted? The file length is 100 and key length is 15

BXEnter Cmd000
H***H01 000 ::PAYMENT HISTORY REPORT FOR HRP
H***H01 001 //GSSXXXX JOB XXXXX,'GENESYS OLPHRPTH',PRTY=12,
H***H01 002 // REGION=5100K,CLASS=A
H***H01 003 // JCLLIB ORDER=GENESYS.PROCLIB
H***H01 004 //JOBLIB DD DSN=GENESYS.LOADLIB,DISP=SHR
H***H01 006 //* DD DSN=SYS1.CEE.V1R5M0.SCEERUN,DISP=SHR

expat · Posted: Fri Mar 16, 2007 4:37 pm

I would somehow doubt that the OS is adding the record.

Have a gooooood long look at everything your program is doing, because the operating system does not hijack programs and insert spurious records into files.

If it does, I think you may have just discovered the very first hack into a mainframe

dick scherrer · Posted: Fri Mar 16, 2007 9:53 pm

Hello,

Does this record still exist in the output file?