EXECUTION OF MAED-1

This section describes the necessary steps to catalogue and delete the various files used by MAED-1, along with the data cards, formats, etc. needed for execution of the various modules. Execution of these activities depends on the operating system and facilities which are available at the user's computer installations.

In this respect, an IBM 3081/3032 computer is available at the IAEA. This uses the MVS (multiple Virtual Storage) operating system, and under this, TSO (Time Sharing Option) is running. In addition, handling of catalogs and data sets is performed by VSAM (Virtual

Storage Access Method). Further, some software products and program utilities are available. For example, the LIBRARIAN software is used for handling data (LIBRARIAN is a generalised data storage and retrieval system marketed by Applied Data Research). Another

software (TELL-A-GRAF, marketed by Integrated Software Systems Corporation) and a combined VARIAN (electrostatic printer plotter)

device are used for producing plots on a computerized basis.

Owing to the fact that not all computer installations are provided with these facilities, the description which follows

is based on execution of the above mentioned steps on IBM operating system (OS) using as catalog and data set handling method BSAM

(Basic Storage Access Method). Appendix A of this Manual describes the main differences in the steps required to execute the activities explained in this section on the facilities available at IAEA (i.e., MVS-TSO-VSAM). Some other slight differences between the execution of MAED-1 as explained in Sections 4 through 7 and as it is normally executed at the IAEA are also explained in Appendix A.

3.1 Description of card deck

The execution of the MAED-1 computer program requires a deck of cards consisting of: job cards, control and data cards, and an end of job card as illustrated in Figure 3.1. It should be noted that all these cards must be in the proper sequence for the program to operate. Except for the data cards (standard 80-columns computer cards), these cards depend on installation standards. The following paragraphs describe how these decks are prepared.

3.2 Job cards

Job card(s) identifying the computer run and describing the type of run in terms of accounting information, user identification, estimated time, etc. are necessary since the computer automatically assigns a priority to each job, and schedules the running of the job accordingly.

- 26

-Figure 3.1 Card deck to execute a MAED-1 module

//NEMMAED1 JOB (BI,P),'ROOM-NAME',CLASS=I,NOTIFY=UID,MSGCLASS=A,

// TIME=(,25)

//.

//* EXAMPLE OF JCL FOR EXECUTING A MAED-1 MODULE //*

//STEPO EXEC 'MODULE.NAME',STEPLIB='USER.LOADLIB' //FT01F001 DD DSN='USER.LIBRARY(MEMB.NAME)',DISP=SHR //FT06F001 DD SYSOUT=A

//

// .

-END

//

Figure 3.2 Cataloguing of MAED-1 files

//ALLOCATE EXEC PGM=IEFBR14

//FT12F001 DD DSN=XBIM.CASENA.LOADSCEN,

// SPACE=(TRK,(1,2)),DCB=(RECFM=FB,BLKSIZE=1600,LRECL=80), // UNIT=SYSDA,DISP=(NEW,CATLG,DELETE)

//FT13F001 DD DSN=XBIM.CASENA.LOADYEAR,

// SPACE=(TRK,(1,5)),DCB=(RECFM=FB,BLKSIZE=1600,LRECL=80), // UNIT=SYSDA,DISP=(NEW,CATLG,DELETE)

//FT14F001 DD DSN=XBIM.CASENA.LOADWASP,

// SPACE=(TRK,(1,2)),DCB=(RECFM=FB,BLKSIZE=1600,LRECL=80), // UNIT=SYSDA,DISP=(NEW,CATLG,DELETE)

//FT15F001 DD DSN=XBIM.CASENA.LOADPLOT,

// SPACE=(TRK,(1,2)),DCB=(RECFM=FB,BLKSIZE=1600,LRECL=80), // UNIT=SYSDA,DISP=(NEW,CATLG,DELETE)

//FT17F001 DD DSN=XBIM.CASENA.LOADCHRO,

// SPACE=(TRK,(1,2)),DCB=(RECFM=FB,BLKSIZE=1600,LRECL=80), // UNIT=SYSDA,DISP=(NEW,CATLG,DELETE)

Figure 3.3 Deletion of MAED-1 files

//DELETE EXEC PGM=IEFBR14

//DD1 DD DSN=XBIM.CASENA.LOADSCEN, // DISP=(OLD,DELETE)

//DD2 DD DSN=XBIM.CASENA.LOADYEAR, // DISP=(OLD,DELETE)

//DD3 DD DSN=XBIM.CASENA.LOADWASP, // DISP=(OLD,DELETE)

//DD4 DD DSN=XBIM.CASENA.LOADPLOT, // DISP=(OLD,DELETE)

//DD5 DD DSN=XBIM.CASENA.LOADCHRO, // DISP=(OLD,DELETE)

- 27

-3.3 Cataloguing of files

For each study to be carried out by the use of MAED-1, it is necessary to allocate the several files previously mentioned in the description of the program organization (see Section 1). The control cards for doing this are shown in Figure 3.2 for a MAED-1 sample problem, "CASENA", on private disc.

It can be seen in this figure that the five MAED files, i.e.,

"LOADSCEN", "LOADYEAR", "LOADWASP", "LOADPLOT" and "LOADCHRO" are all "allocated", that is they are prepared to be written on before they are read (at this stage they contain no information). At IAEA, names for MAED-1 case studies must be made of an initial alphabetic character, followed by up to five characters which can be alphabetic or numeric. Examples of names for case studies are: ALGER1, CASENA, INDONE, MEXI#2, WORLDA, etc.

Sometimes it is necessary or desirable to delete files, and the control cards for doing this are shown in Figure 3.3.

3.4 Control Cards

Figure 3.4 lists the control cards required for standard execution of the MAED modules 1 through 4 in the same order. It can be seen in this figure that the group for each module is composed of several control cards. The first two cards, in each case, identify the particular MAED-1 module (i.e., PGM= in first card) and where it is stored (i.e. the USER.LOADLIB library in second card).

The subsequent control cards specify in each case: data sets to be used as input, data files controlling the printed output and the files to be written on or read by the respective module during its execution.

Input data needed by each module to run are stored as members of a user's library (or eventually as data files) and these data sets names must be defined as parameter DSN of the appropriate card.

Due to the variety of data required by modules 1 and 2, more than one card identifying data sets are required by these modules.

Files FT06 and FT08 are reserved for controlling the program printout. The use of "SYSOUT=A" on these files results in standard printed output, which can be changed to different types of output (for example, on plain white paper) by using the appropriate SYSOUT parameters depending on the operating system. Again, owing to the large amount of information developed in module 1, more than one SYSOUT cards are required by this module.

Concerning the input and output files used by each module, each file is also identified by its number and name (e.g. FT12 and DSN=XBIM.CASENA.LOADSCEN). Once more, owing to the large amount of information to be handled by some modules (modules 1 and 3) during their execution, some scratch files (FTll for Module 1 and FT16 for Module 3) are used as temporary work files by these modules.

- 28

-It must be emphasized here that, except for the case name, everything on the control cards should be exactly as shown in Figure 3.4, including blank spaces, commas and periods.

At IAEA, execution of each MAED-1 module is controlled by means of some procedures, which have been written and stored (catalogued) in a procedure library. Appendix A describes the main features of these procedures, along with the control cards required to execute the modules at the IAEA computer facilities. The runs for the sample problem developed for this manual (CASENA) were carried out using the control cards shown in Appendix A. In the following sections, however, execution of the various MAED-1 modules will be described according to the control cards of Figure 3.4. It is believed, this will provide a better understanding of the different files used as

input or output by each module.

3.5 Data Cards

The input data for each module will be discussed one at a time in the respective sections of this manual describing the execution of the module. Generally speaking, the format of the input data is very important since the machine will reject or misinterpret data which are not presented in the form specified. The format specifies both, the input information and the column numbers (i.e. the field)

in which it must appear:

The "I" format specifies an integer number with no decimal point being allowed; it is necessary that the integer appear at the right-hand side of its field, i.e. it is "right adjusted", so that any blanks to the right of a number will be interpreted by the computer as zeroes (e.g. a "5" appearing in the first column, from left to right, of a four column field will be interpreted as "5000").

On the other hand, the "F" format specifies a floating point decimal number which is not necessary to be adjusted to the right of the

field. Generally speaking, the decimal point should always be included in the field, even if there are no numbers to the right of the decimal point. Finally, the "A" format (alphanumeric) specifies any combination of letters, digits or special characters which can be accepted by the computer (such as asterik '*', ampersand '&', dollar '$', etc.)

3.6 End-of-Job Card

The last card of the deck is the end-of-job card. If more than one MAED module is to be run in a single job (i.e. using only one job card) the decks for the various modules would be placed one behind the other (in the same order as they are wanted to be run) with the end-of-job appearing only once at the end of the last deck.

- 29

-Figure 3.4 Control cards to execute the MAED-1 modules

//GO EXEC PGM=XBIMMll

//STEPLIB DD DSN=USER.LOADLIB,DISP=SHR //GO.FT01F001

//GO.FT02F001 //GO.FT03F001 //GO.FT04F001 //GO.FT06F001 //GO.FT08F001 //GO.FTllF001

DD DSN=XBIM.MAED.PROG(M1INPSD),DISP=SHR DD DSN=XBIM.MAED.PROG(M1INPCP),DISP=SHR DD DSN=XBIM.MAED.PROG(M1INPTP),DISP=SHR DD DSN=XBIM.MAED.PROG(M1TABLE),DISP=SHR DD SYSOUT=A

DD SYSOUT=A DD DSN=&&TEMP,

// UNIT=SYSDA,DISP=(,DELETE),SPACE=(TRK,(5,1)), // DCB=(RECFM=VBS,LRECL=2404,BLKSIZE=7216) //GO.FT12F001 DD DSN=XBIM.CASENA.LOADSCEN,DISP=OLD

//GO EXEC PGM=XBIMM12

//STEPLIB DD DSN=USER.LOADLIB,DISP=SHR

//GO.FT01F001 DD DSN=XBIM.MAED.PROG(M2INPS1),DISP=SHR //GO.FT02F001 DD DSN=XBIM.MAED.PROG(M2INPS2),DISP=SHR //GO.FT05F001 DD DSN=XBIM.MAED.PROG(M2INPU5),DISP=SHR //GO.FT06F001 DD SYSOUT=A

//GO.FT12F001 DD DSN=XBIM.CASENA.LOADSCEN,DISP=SHR //GO.FT13F001 DD DSN=XBIM.CASENA.LOADYEAR,DISP=OLD

//GO EXEC PGM=XBIMM13

//STEPLIB DD DSN=USER.LOADLIB,DISP=SHR

//GO.FT05F001 DD DSN=XBIM.MAED.PROG(M3INPU5),DISP=SHR //GO.FT06F001 DD SYSOUT=A

//GO.FT13F001 DD DSN=XBIM.CASENA.LOADYEAR,DISP=SHR //GO.FT14F001 DD DSN=XBIM.CASENA.LOADWASP,DISP=OLD //GO.FT15F001 DD DSN=XBIM.CASENA.LOADPLOT,DISP=OLD //GO.FT16F001 DD DSN=&&TEMP,

// UNIT=SYSDA,SPACE=(TRK,(l,1)),

// DCB=(RECFM=FB,LRECL=80,BLKSIZE=1600)

//GO EXEC PGM=XBIMM14

//STEPLIB DD DSN=USER.LOADLIB,DISP=SHR

//GO.FT05F001 DD DSN=XBIM.MAED.PROG(M4INPU5),DISP=SHR //GO.FT06F001 DD SYSOUT=A

//GO.FT17F001 DD DSN=XBIM.CASENA.LOADCHRO,DISP=SHR

30

-THIS PAGE LEFT BLANK INTENTIONALLY

- 31