Var adm messages not updating

S002 - RECORD IS GREATER THAN 32,768 BYTES, EXCEEDS MAXIMUM TRACK LENGTH OR STATED BLOCKSIZE, COULD NOT BE CONTAINED IN ONE EXTENT, OR TOO MANY TRACKS SPECIFIED FOR CYLINDER OVERFLOW.

IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S002 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S002-RC) DCB HAD THE WRONG BLOCK SIZE IEHMOVE - ATTEMPT TO RENAME DATA SET WHEN NEW NAME ALREADY EXISTS WRONG RECORD FORMAT SPECIFIED IN JCL S002 - 04 - AN INVALID RECORD WAS ENCOUNTERED ON A GET OPERATION.

THE RDW FOR A VARIABLE LENGTH RECORD SPECIFIES A LENGTH GREATER THAN 32,752.

S002 - 14 - AN INVALID RECORD WAS ENCOUNTERED ON A PUT OR WRITE OPERATION.

S001 - 05 - FOR QSAM, A GET WAS ISSUED AFTER END-OF-FILE.

THE RECORD LENGTH IS GREATER THAN THE BLOCKSIZE SPECIFIED IN THE DCB.

S002 - 18 - AN INVALID RECORD WAS ENCOUNTERED ON A PUT OPERATION; THE DATASET USES THE VARIABLE RECORD FORMAT.

THIS COULD ALSO OCCUR IF ALLOCATION OF THE PRIMARY EXTENT WAS NON-CONTIGUOUS AND ANY OF THE SECONDARY EXTENTS WERE SMALLER THAN THE BLOCK.

S002 - 28 - THE ERROR OCCURRED DURING THE CREATION OF A DIRECT DATASET.

Leave a Reply