FSU Processing and Space Requirements

  1. The z/VSE library structure must exist. This means that the FSU depends on having IJSYSRS.SYSLIB, PRD1, PRD2.CONFIG, PRD2.SCEEBASE, PRD2.SAVE, PRD2.TCPIPC, and PRD2.TCPIPB available. If you have combined or renamed these libraries and sublibraries, the FSU job stream will not work without modification.

    System volumes must be DOSRES and SYSWK1. Also, the VSE/VSAM user catalog VSESPUC must be available.

  2. Do not run FSU stage 1 if you performed a BASIC startup. It will overlay your VSE/POWER files.
  3. The FSU runs per default in the background partition (BG). You can, however, run the job stream in any partition as long as the partition leaves enough space for MSHP (at least 1280KB, plus 256KB partition GETVIS area), except partition FB. However, in stage 2 the jobs are forced to run in BG and only the following partitions are started: BG, F1, F2, F3, F4, F5, and FB with the basic security manager.
  4. The FSU job sequence is managed by the Job Manager. Only one job sequence from the stage 1 dialogs should be in the reader queue at one time.
  5. In stage 2 the FSU defines a work file for the text repository file. The work file is defined in VSAM space. You should make sure that your system has sufficient VSAM space on the disk device you have specified in the dialog Verify Location of Involved Serviced Files for the definition of this work file. To check this:
    • Verify if you have changed the location of the VSAM catalog in the dialog Verify Location of Involved Serviced Files.
    • Estimate the required space for the work file by looking at the space your current text repository file uses. Access the File and Catalog Management catalog, enter VSESPUC (or the catalog name you want to use) for CATALOG NAME, choose selection 1 and use option 1.
    • Check how much VSAM space is free in the VSESPUC catalog you have specified in the Verify Location of Involved Serviced Files dialog (Fast Path 141) on the specified disk device. The default is VSESPUC. Choose selection 5 of the File and Catalog Management dialog and use option 1. If there is not sufficient space left, use option 4 to define new space.

      For the Text Repository workfile, you do not need to define or move any clusters. FSU uses the data specified for it to do so.