//I40   DD  DSN=FMU.DATA,DISP=(OLD,PASS),UNIT=TAPE,
//        VOL=SER=volid,LABEL=(40,SL)
 .
 .
 .
//O40   DD  DSN=prefix.FMU.DATA,DISP=OLD
 .
 .
 .
 COPY   INDD=I40,OUTDD=O40

ALLOC F(ISHFALOC) DA('prefix.ISHFALOC.DATA') NEW CATALOG -
SPACE(5,5) TRACKS LRECL(80) RECFM(F B) BLKSIZE(23440) DIR(30)

Note: Sites can customize the ToolKit for user groups by creating separate ISHFALOC data sets for each group. Step 5 must be executed for each group/data set.

To prepare the background window for the ToolKit, you are asked for the company name, a support center phone number, the installation date, the Information Builders FOCUS Site Code, a default printer destination, and a list of optional printer destinations. The company information is then displayed on the background of the ToolKit Menuing system. The printer information is used to assign a default printer when first executing the ToolKit and allows users to change their print destinations easily. You supply this information on simple fill-in-the-blank screens.

1. Enter FOCUS with your FOCUS CLIST.
2. Execute the ToolKit Installation Procedure.

   EX ISHFINST
   Enter company name at the prompt and press ENTER.
   Enter telephone number for support at the prompt and press ENTER.
   Enter install date (in MM/DD/YY format) at the prompt and press ENTER.
   Enter the FOCUS site code at the prompt and press ENTER.
   Enter the default printer at the prompt and press ENTER.

   The format for the printer prompt is: 'c (node.)dest', where 'c' is the one-character sysout class, node is the JES printer node, and dest is the JES destination parameter. The node and dest parameters are optional and, when provided, must be separated from the sysout class by a single blank.

   Reply to the prompt for additional company printer IDs that can be selected by the user. If the reply is no, installation is complete. If the reply is yes, enter the additional printers in the format: one-character sysout class, 17-character node and destination (node.dest where node is optional), and 30-character description. The sysout class cannot be blank or zero (you may delete entries by blanking out the sysout class). Note that the first printer in the list will be assigned as the user's default printer. You may also designate a data set as the output by providing an arbitrary sysout class, a destination code of DISKFILE, and the low-level qualifiers of the data set name as the description. The user's user ID will be prefixed to this name. The data set must be typed in uppercase (all capitals), as it will not be translated. Up to 18 printers can be added at this time, including the default printer. Changes can be made after installation by allocating the ISHFALOC data set and executing FOCEXEC ISHFPNTR, or by editing the member ISHDPNTR in the ISHFALOC data set (be sure to maintain columnar spacing).

   When the installation is complete, the ToolKit will be executed. Move the cursor to the last option (EXIT) on the menu and press ENTER.

The ToolKit permits batch submission of FOCEXECs by users. The JCL submitted must be customized for site data-set naming and JOBCARD standards.

1. Edit member ISHFBJCL in FOCEXEC.DATA.

   Replace the job card information with a site-specific job card. The variable &&USER, which is the user ID set in the ToolKit startup program (ISHFSHLL), may be used in the job card.

   Replace the data set names for STEPLIB, ERRORS, FOCEXEC, MASTER, and FOCSQL (where appropriate), with the site-specific data set names for the FOCUS data sets.

2. Edit member ISHFBTCH in FOCEXEC.DATA.

   Delete the following lines that preclude batch execution until the JCL has been updated in the previous step (6a).

   -SET &&ERROR='BATCH EXECUTION NOT INSTALLED-SEE DOCUMENTATION';
   -GOTO EXIT

   To provide direct submission of the generated JCL in TSO, remove the comment characters (-*) from the following lines:

   -* DYNAM SUBMIT &BATCHJCL
   -* -GOTO DONE

   Otherwise, the JCL will be displayed in TED. The user may then submit the batch job by typing SUBMIT on the TED command line.

The ToolKit z/OS Utilities and FOCUS Utilities menus support copying of data sets and members in TSO (but not MSO) by utilizing the TSO COPY command. If your site supports the COPY command, proceed to Step 8. If not, you will have to disable this function as follows:

1. Edit member ISHFEDTF in FOCEXEC.DATA.

   After the -COPY label, insert the following lines:

   -SET &&ERROR='COPY option is not available at -company name-';
   -GOTO STRT

2. Edit member ISHFTUTL in FOCEXEC.DATA.

   After the -PDSCOPY label, insert the following lines:

   -SET &&ERROR='COPY option is not available at -company name-';
   -GOTO TOP

Many ToolKit options allow users to write to their own data sets. To that end, the ToolKit assumes that users' files will follow the suggested Information Builders data-set-naming convention:

userid.FOCEXEC.DATA 
userid.MASTER.DATA 
userid.FOCDEF.DATA  (optional) 
userid.FOCSQL.DATA  (optional) 
userid.filename.FOCUS

(where filename is the Master File name that describes the FOCUS data source)

If your site follows these conventions, continue with Step 9. Otherwise, you may alter these assumptions as follows:

1. Change high-level qualifier only.

   Edit ISHFSHLL in FOCEXEC.DATA. Change the following line to return the desired value (the default is userid).

   -SET &&USER=GETUSER('A8');

   Note: If &&USER was used in ISHFBJCL in JOBCARD processing (Step 6), modifications must be made in that program as well.

2. Change the low-level qualifiers.

   Edit ISHFSHLL in FOCEXEC.DATA.

   Change the following lines to return the desired value.

   -SET &DEFMAS = &&USER ||'.MASTER.DATA';
   -SET &DEFFEX = &&USER ||'.FOCEXEC.DATA';
   -SET &DEFSQL = &&USER ||'.FOCSQL.DATA';
   -SET &DEFDEF = &&USER ||'.FOCDEF.DATA';

   Edit ISHFFOCM in FOCEXEC.DATA.

   Change the following lines to return the desired value.

   -SET &DSN=&&USER || &MASTNAME ||'.FOCUS';

3. Pre-allocation of user program data sets.

   The ToolKit will attempt to allocate the program data sets to ddnames ISHXFOCX, ISHXMAST, ISHXFDEF, and ISHXFSQL, unless those ddnames have been pre-allocated. Therefore, you may pre-allocate any user data set (a PDS with LRECL 80) to these ddnames prior to executing the ToolKit and those allocations will be respected. (You must still change the ISHFFOCM program in the previous step). It is recommended that these data sets also be concatenated to ddnames FOCEXEC, MASTER, FOCDEF, and FOCSQL.

4. Dynamic allocation of user program libraries.

   If the files were not pre-allocated and the user data set is not found, the ToolKit will allocate, to the ddnames ISHXFOCX, ISHXMAST, ISHXFDEF, and ISHXFSQL, the first data set in the concatenation of ddnames FOCEXEC, MASTER, FOCDEF, and FOCSQL, as follows:

   ISHXFOCX=FOCEXEC
   ISHXMAST=MASTER
   ISHXFDEF=FOCDDEF
   ISHXFSQL=FOCSQL

The ToolKit will attempt to dynamically access FOCUS, sequential, and comma-delimited files identified to the ToolKit. This is accomplished by creating a FOCEXEC that performs the necessary allocations and USE commands for a given data source. This FOCEXEC is stored in the ISHFALOC data set, with a member name corresponding with the file name (as used by FOCUS).

For example, to allow the ToolKit to dynamically allocate the CAR FOCUS data source, create a FOCEXEC in the ISHFALOC data set with member name CAR. This FOCEXEC may contain the following:

DYNAM ALLOC FILE CAR DA prefix.CAR.FOCUS SHR REUSE
-EXIT

Note that these members are FOCEXECs and can include any FOCUS commands.

The original FOCEXEC contains the following commands, which support automatic execution of the FOCUS Menu:

-* This FOCEXEC will be executed only after PROFILE FOCEXEC
-* execution has been completed.
-* INCLUDE FMMAIN

Change the FOCEXEC to read:

-IF &FOCMODE EQ 'CRJE' GOTO EXIT;
EX ISHFSHLL
-EXIT

This will allow the ToolKit to execute online only; it will be bypassed in batch.

Note: You may use this FOCEXEC to give users the option of executing the ToolKit, the FOCUS Menu, or exiting to native FOCUS.

EX ISHFSHLL

Note: The DB2 Data Adapter must already be installed to take advantage of ToolKit DB2 features. The DB2 installation creates the prefix.FOCSQL.DATA, prefix.TRF.DATA, and prefix.FOCSQL.LOAD data sets. The installation must also copy AUTODB2 from prefix.FOCSQL.DATA to prefix.FOCEXEC.DATA, as this is used in the ToolKit.

1. CLIST for non-DB2 Data Adapter installation:

   ALLOC F(MASTER)   DA('&SYSUID..MASTER.DATA’  -
                        'prefix.MASTER.DATA')     SHR
   ALLOC F(FOCEXEC)  DA('&SYSUID..FOCEXEC.DATA' -
                        'prefix.FOCEXEC.DATA')    SHR
   ALLOC F(FMU)      DA('prefix.FMU.DATA'         SHR
   ALLOC F(ISHFALOC) DA('prefix.ISHFALOC.DATA'    SHR
   ALLOC F(ERRORS)   DA('prefix.ERRORS.DATA'      SHR
   ALLOC F(USERLIB)  DA('prefix.FUSELIB.LOAD'     SHR
   CALL 'prefix.FOCLIB.LOAD(FOCUS)'

   where:

   prefix

   Is the high-level qualifier for your FOCUS production data sets.

2. CLIST for DB2 installation:

   ALLOC F(MASTER)   DA('&SYSUID..MASTER.DATA'  -
                        'prefix.MASTER.DATA')     SHR
   ALLOC F(FOCEXEC)  DA('&SYSUID..FOCEXEC.DATA' - 
                        'prefix.FOCEXEC.DATA')    SHR
   ALLOC F(FMU)      DA('prefix.FMU.DATA')        SHR
   ALLOC F(TRF)      DA('prefix.FOCSQL.DATA')     SHR
   ALLOC F(FOCSQL)   DA('&SYSUID..FOCSQL.DATA'  - 
                        'prefix.FOCSQL.DATA')     SHR
   ALLOC F(ISHFALOC) DA('prefix.ISHFALOC.DATA'    SHR
   ALLOC F(ERRORS)   DA('prefix.ERRORS.DATA'      SHR
   ALLOC F(USERLIB)  DA('prefix.FOCSQLOAD'      -
                        'prefix.FOCLIB.LOAD'    -
                        'prefix.FUSELIB.LOAD')    SHR
   CALL 'prefix.FOCLIB.LOAD(FOCUS)'

   where:

   prefix

   Is the high-level qualifier for your FOCUS production data sets.

   Note: If you installed the DB2 data adapter using the TSO Attach Facility, replace the CALL statement with the following lines:

   DSN SYSTEM (ssid) 
   RUN PROGRAM(FOCUS) PLAN(plan) LIBRARY('prefix.FOCLIB.LOAD')
   END

   where:

   ssid

   Is the subsystem id of the DB2 subsystem.

   plan

   Is the DB2 application plan.