//STEP3 EXEC PGM=IEBGENER,COND=(4,LT) //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT2 DD DSN=HILEVELQ.EXPSTATS, // UNIT=VTS1,DISP=(NEW,CATLG),LABEL=(3,SL), // VOL=(,,REF=*.STEP1.SYSUT2), // DCB=*.STEP1.SYSUT2 //SYSUT1 DD * EXPORT STATUS 01 /* The information that is required in the export list file is, as for BVIR, provided by writing a  logical volume that fulfills the following requirements: Important:  Ensure that the files are assigned an MC that specifies that only the local  TS7700 has a copy of the logical volume. You can have the ACS routines assign this  MC, or you can specify it in the JCL. These files must have the same expiration dates  as the longest of the logical volumes you export because they must be kept for  reference. With only OPTIONS1,COPY (without EJECT), the physical volumes are placed in  the export-hold category for later handling and left in the library by an operator. – That logical volume must have a standard label and contain the following files: GLYPH<129> An export list file, as created in step 1 in Example 13-4 on page 755. In this  example, you are exporting Pool 09. Option EJECT in record 2 tells the TS7700 to  eject the stacked volumes upon completion.  GLYPH<129> A reserved file, as created in step 2 in Example 13-4 on page 755. This file is  reserved for future use. GLYPH<129> An export status file, as created in step 3 in Example 13-4 on page 755. In this file,  the information is stored from the Copy Export operation. You must keep this file  because it contains information that is related to the result of the Export process  and must be reviewed carefully.  – All records must be 80 bytes.  – The export list file must be written without compression. Therefore, you must assign a  Data Class (DC) that specifies COMPACTION=NO or you can overwrite the DC  specification by coding TRTCH=NOCOMP in the JCL. 756  IBM TS7700 Release 5.0 Guide