Previous Topic: $BANNER and $$FIRSTNext Topic: RMOPSF - Form and Page Definition Modification


Using RMOPSF to Correct Banner Page Problems

To use RMOPSF to correct banner page problems, follow these steps:

  1. Determine the PAGEDEF or FORMDEF resource you want to use as a model; ensure that it correctly formats the banner page you use.

    Note: You can create a PAGEDEF or FORMDEF in a new member or use a PAGEDEF or FORMDEF defined in a member that IBM provides.

  2. Prepare the JCL code that executes RMOPSF: include the MDLFDEF or MDLPDEF control statement to specify the name of the model you want to use, and include the SELECT control statement to prevent all members in the input library from being processed.
  3. Execute the RMOPSF job.
  4. Did you allocate the output library for RMOPSF to the AFP PSF task (does the new library data set name differ from the old library data set name)?
  5. Will you use the banners TSTBNDL, TSTDIST, and TSTRPT provided with CA Deliver?

Important! Do not insert $BANNER and $$FIRST records into banner pages stored in AFP resources; instead, modify banner pages stored in the database.

Note: You do not need to recycle the started task to load these members.

  1. Did you change or add the name of any member in CAI.CVDED133 when you loaded it?
  2. Execute the job that generates your report.

    When the report is printed by the AFP subsystem, the special commands in the banners switch to the data map or medium map with the $BANNER label to print the start banner page, switch to the page format or overlay group with the $$FIRST label to print the report data, and then switch back to the $BANNER label to print the end banner page.

    Note: RMOPSF supports a wide range of page and form definition resources but not all. For example, page and form definition resources that contain conditional logic are not currently supported.