Setting up the AFRREBLK profile

To set up an optional AFRREBLK profile, you copy the sample profile in SYS1.SAMPLIB (AFRREBLK) to a data set named userid.AFRREBLK.PROFILE, where userid is your user ID.

The AFRREBLK profile includes a list of possible AFP object types that the reblocking program can recognize. You can set up the AFRREBLK profile to include the default data set names you want. To specify a partitioned data set, use the high-level qualifier and the data set name. To specify a sequential data set, use only one qualifier. If you specify the name as a partitioned data set, you must preallocate the data set. For a sequential data set, the one qualifier specified is used as the third qualifier in the data set name. Figure 47 shows the sample AFRREBLK profile that is included with PSF.

Figure 47. Sample AFRREBLK profile

/****************************************************************************/
/*  Function: AFRREBLK MVS Profile - used when the output file is           */ 
/*            not specified.  The program will determine the type           */ 
/*            of AFPDS object and store it to the specified                 */
/*            location.                                                     */
/*                                                                          */ 
/*  Syntax  : Keyword DatasetName                                           */
/*                                                                          */
/*            The DatasetName may be a partition dataset name or a          */
/*            single name that will be used to create a sequential          */
/*            dataset.  Partition dataset names may use 'userid()'          */ 
/*            as a high level qualifier and will be resolved to             */ 
/*            the userid of the person running the program.                 */ 
/*            Partition datasets must be preallocated.                      */
/****************************************************************************/

FontUB   userid().afrreblk.fontub            /* Unbounded-Box Font Names    */
Font240  userid().afrreblk.font240           /* 240 Bounded-Box Font Names  */
Font300  userid().afrreblk.font300           /* 300 Bounded-Box Font Names  */
FontOLN  userid().afrreblk.fontOLN           /* AFP Outline Font Names      */

PageDef  userid().afrreblk.pagedef           /* Page Definition Names       */
FormDef  userid().afrreblk.formdef           /* Form Definition Names       */

Doc240   userid().afrreblk.doc240            /* 240 pel Document Names      */
DocAFP   userid().afrreblk.docafp            /* Resolution Independent Doc  */

Ovly240  userid().afrreblk.ovly240           /* 240 pel Overlays            */
OvlyAFP  userid().afrreblk.ovlyafp           /* Resolution Independent Ovly */

IOCA     userid().afrreblk.ioca              /* IOCA Images                 */
PageSeg  userid().afrreblk.pageseg           /* IM1 Image - Page Segments   */

Pseg240  userid().afrreblk.pseg240           /* 240 Pel Image Descriptor    */
PsegAFP  userid().afrreblk.psegafp           /* 300 Pel Image descriptor    */
AFPOBJ   userid().afrreblk.afpobj            /* Object Container            */

LRECL    32756                               /* Record Length               */
BLKSIZE  32760                               /* Blocksize                   */

Each line of the AFRREBLK profile contains one keyword and its value, separated by one or more spaces. Any line with an unrecognized keyword is ignored. You can enter keywords in uppercase or lowercase. Valid keywords are: