AVAS V4.0A Job Management - Fujitsu Technology Solutionsmanuals.ts.fujitsu.com/file/976/avas_avw.pdf · The "AVAS Ready Reference" [1] contains an overview of the statements and operands,

U5184-J-Z125-7-76 1

1 Preface

1.1 Brief product description

The complexity and workload of computer centers are constantly increasing. DP operationstherefore require clear structuring, high levels of transparency and flexibility, and constantproductivity gains.

AVAS enables the computer center to automate its production jobs and to handle thenecessary planning, preparation and monitoring tasks interactively. AVAS supports bothdecentralized work scheduling in the various non-DP departments and the central storageof information on jobs.

The net description defines the arrangement of jobs in the net, timing specifications, jobcharacteristics, restart variants, and dependencies on other nets and jobs, and on conditionvalues and resources. Time scheduling uses calendars with symbolic dates or procedurenames which, together with the net descriptions, form a production plan. During productionpreparation, it is possible to supply the nets with runtime parameters from the productionplan via user masks or from parameter files. During the release for production, transport listsand tape mount listings can be created for the required data volumes by accessing theMAREN catalog. After the net has been released, it is started by the run control system inthe production execution stage in accordance with the predefined time specifications anddependencies.

Production monitoring, like all of the preceding steps, is carried out online. If an error occurs,predefined restart processing is activated. Depending on the specifications in the net,restart is either executed automatically or initiated explicitly by the user, the latter permittingfurther manual intervention. The entire production sequence within the planned nets islogged and can be reconstructed on the basis of the journal. Under AVAS, the runtime logsof jobs can be saved and displayed.

The AVAS facilities are also available in a homogeneous BS2000/OSD multiprocessornetwork (HIPLEX MSCF). Here the HIPLEX MSCF (Multi System Control Facility) functionsare used for job distribution and monitoring, and the definition, preparation and monitoringof production can be performed centrally from a single AVAS system. Furthermore, AVAScan start and monitor jobs on server systems from the BS2000/OSD platform.

2 U5184-J-Z125-7-76

Preface

The AVAS functions may be subdivided into two basic areas:

– production definition or job managementi.e. the generation of the requisite data structures such as net and job descriptions,documentation, parameters, and the time schedule for processing under AVAS, and

– production execution or job handlingi.e. implementation of the production run at the scheduled time on the basis of the datastructures generated.

1.2 Target group

This manual describes the menu system and statements available to the user for jobmanagement within the AVAS system.

1.3 Summary of contents

Job management under AVAS involves various work stages in which the basic data forproduction is created. This manual is divided into the following sections in accordance withthese stages:

– interactive mode with AVAS; mask structure and operation

– creation of nets, jobs, server jobs, S procedures and documentation elements

– creating and editing condition descriptions and

– time scheduling via calendars

In addition, this manual also describes the use of AVAS in conjunction with the data volumemanagement system MAREN and the AVAS-QUER utility routine.

The work stages involved in job handling are described in the “AVAS Job Handling“ manual[2].

Both manuals are intended as reference works, and presuppose a basic knowledge of theAVAS system. This knowledge can be obtained by attending an AVAS course.

The "AVAS Ready Reference" [1] contains an overview of the statements and operands, agraphic representation of the mask sequences accompanied by the operation codes, andan overview of the statuses of the nets, condition descriptions and logs. The ReadyReference is divided into a section for users and a section for the AVAS administrator, andcontains all messages of the AVAS system.

U5184-J-Z125-7-76 3

Preface

A separate manual, "AVAS for the Administrator" [3], has been produced for AVAS systemadministration.It describes all the tasks the AVAS administrator has to perform - from system generationto administration of the AVAS system, including the management of runtime logs, theBATCH functions, the external creation of nets, jobs/procedures and documents throughprograms, the computer center exits, the program interface, installing AVAS-DOORS, multi-processor operation with AVAS, and starting and monitoring tasks on server systems.

README file

Information on functional changes and additions to the current product version described inthis manual can be found in the product-specific README file. You will find the READMEfile on your BS2000 computer under the file name SYSRME.product.version.language. Theuser ID under which the README file is cataloged can be obtained from systems support.You can view the README file using the /SHOW-FILE command or an editor, and print itout on a standard printer using the following command:

/PRINT-DOCUMENT filename, LINE-SPACING=*BY-EBCDIC-CONTROL

or, for SPOOL versions earlier than V3.0A:

/PRINT-FILE FILE-NAME=filename,LAYOUT-CONTROL=PARAMETERS(CONTROL-CHARACTERS=EBCDIC)

4 U5184-J-Z125-7-76

Preface

1.4 Changes since the last version of the manual

Compared to the previous version, V4.0A of AVAS incorporates the following importantchanges:

Century change

With AVAS V4.0A, all internal functions and all internal data structures are converted tofour-digit year specifications, or are changed in such a way that AVAS handles two-digityear specifications in the period from 1981 to 2080 correctly.

The date display in the AVAS masks has not been changed in this regard, and so theinterface is virtually unchanged.

The output date in the journal records has been changed to a four-digit year:old date format: .....'981028123000'.....new date format: .....' 19981028123000'.....

Version 4.0A of AVAS processes both formats.

The journal records are still transferred in the version 3.0A format on the CC exitAVEX0001.The new format of the journal records is transferred on the new CC exit AVEX0002.

All journal records are backed up in the new format.

If journal records of both versions have to be merged for evaluation purposes, the olddate format must be converted to the new date format (e.g. using the software productPERCON).

Example

/PROC C/REMARK *****************************************************************/REMARK PERCON JRNDAT.SAVE AVAS V3 FORMAT TO AVAS V4 FORMAT/REMARK *****************************************************************/SYSFILE SYSDTA=(SYSCMD)/SET-FILE-LINK FILE-NAME=JRNDAT.SAVE.ALT,LINK=PCIN/FILE JRNDAT.SAVE.CONV,FCBTYP=SAM,LINK=PCOUT/START-PERCON SET-REC-MAP OUT-LINK-NAME=*STD, - OUT-FIELDS=(FIELD(IN-POS=5,IN-LEN=44, - OUT-POS=5,OUT-LEN=44,OUT-FOR=IN-FOR), - ' 19'(OUT-POS=49,OUT-LEN=4,OUT-FORM=CHAR), - FIELD(IN-POS=49,IN-LEN=REC-LEN(RED=44), - OUT-POS=53,OUT-LEN=STD,OUT-FOR=IN-FOR)) START-CONV END/SYSFILE SYSDTA=(PRIMARY)

U5184-J-Z125-7-76 5

Preface

/SKIP .ENDE/STEP/REMARK ERROR/.ABEND ABORT/.ENDE ENDP

The century change does not involve any changes for the user on the BATCH interface.

The date is still transferred with a two-digit year on the program interface, which meansthat the application programs do not have to be changed.However, users must check to see whether undefined states in relation to the two-digityear specifications arise in their programs at the change of the century.

Calendar functions

When you create an AVAS calendar (CREATE-CALENDAR), symbolic start dates(SYSTEM symbolic dates) can be generated automatically.

If you specify the parameter SYMDAT-NAME for CREATE-CALENDAR, the followingsymbolic start dates are generated, depending on the values assigned:

SYMDAT-NAME=*STD- every day- working day- nth working day of the month- nth day of the month- last working day of the month

SYMDAT-NAME=*ALLIn addition to the symbolic start dates generated for *STD, combina-tions of day of the week, month, working day and day of the monthare generated (see the CREATE-CALENDAR statement).

Up to 98 symbolic start dates can be entered on a calendar day. The symbolic startdates for the user (USER symbolic dates) can also be processed using EDT. GeneratedSYSTEM symbolic dates cannot be entered or changed.

A differentiation is made between WORK, NWRK and FREE for the properties of a day.On a day with TYPE=NWRK, a processing operation is planned if the net symbolic dateis found for day.When relative net symbolic dates are used for planning (symdat ±n), no processing isplanned for a day with TYPE=NWRK.

6 U5184-J-Z125-7-76

Preface

Period functions

Periods with a variable start date and end date (standard periods) can be defined usingthe BATCH statement CREATE-PERIOD. The PERIOD-START-DATE and PERIOD-END-DATE for these periods change with the current date.Periods can now also be used for SHOW-JOURNAL, START-NET, RESTART-NET andfor reorganizing in order to select elements.

Password change

If users change their passwords in BS2000, they can also announce the change withdirect effect for their jobs and procedures to be started with AVAS using CHANGE-NET-DESCRIPTION (in batch mode). The AVAS run control system then uses the newpassword to start even the jobs and procedures of nets that have already beenreleased. This involves exchanging the old password for the new password after adefined validity period.

Wildcard support

The operands NET-NAME, JOB-NAME and DOCUMENT-NAME can also be specifiedin BS2000 wildcard syntax in order to select elements from the assigned libraries andfiles.

Time settings for starting and restarting nets

The parameters EARLIEST-START, LATEST-START and LATEST-OCCURE can bechanged for nets with the status OPWAIT, WAITING, HOLD and ERROR using thestatements START-NET, HOLD-NET, RESUME-NET, RESTART-NET and CANCEL-NET (with CANCEL-TYPE=SOFT).EARLIEST-START can be defined directly. The parameters LATEST-START andLATEST-OCCURE are changed by the specified time span in days, hours and minutesfor all structure elements by presetting the time shift MODIFY-LATEST. MODIFY-LATEST can also be used to change the OCCURE-TIME parameter for “Wait for time“.

Users’ system variables S#nnn

Users can define their own S#nnn system variables using the MODIFY-SYSTEM-PARAMS statement, thereby modifying their jobs and procedures.The user variables S#nnn, which are valid throughout the system, can also bepredefined using the generation parameters.

U5184-J-Z125-7-76 7

Preface

Reorganizing nets, journals and logs

During reorganization, nets can be selected from the PERDAT on the basis of periods.If the new variable periods are used for this purpose, invariant reorganization jobs canbe created.In order to reduce the amount of resources used, a number of reorganization runs canbe performed once the programs have been loaded. In addition, a separate output filecan be assigned to each net while backing up the journals and logs.The individual runs are started using the reorganization statement START.

AVAS users with no signon lock

No signon lock is set following CANCEL-USER for users who are authorized to use theMODIFY-SYSTEM-PARAMS statement.

AVAS system monitoring in HIPLEX

In an MSCF network, the run control system monitors the systems that are assignedtasks using an MSCF monitoring job variable. This is supplied by MSCF in BS2000/OSD V3.0A or later. In earlier versions of BS2000/OSD, the monitoring job variablemust be set up and managed by the system administrator.

Support for the ENTER parameter HOST=*ANY

The NET/JOB-CAT parameter can be described using the value *ANY in the net or jobdescription.In this case, the run control system uses the new JMS job distribution (in BS2000/OSDV3.0A or higher in the XCS network) to determine the catalog ID of the system for thejob run, and the task is started there.

AVAS agent for Windows NT

Processing can be started and monitored on systems running under Windows NT usingthe AVAS agent for Windows NT via structure elements with FU=X.To do this, the computer connection must be entered in the configuration file and theAVAS agent must be started on the computer.

8 U5184-J-Z125-7-76

Preface

1.5 Notes on upgrading from AVAS V3.0A to AVAS V4.0A

Generation parameters and system parameters

The generation parameters and system parameters can be transferred without changeinto Version 4.0A.The system parameters do not have to be regenerated.

Libraries and files

All AVAS files of Version 3.0A can be taken over into Version 4.0A unchanged.

Nets that have already been planned or released for processing under AVAS V3.0A canalso be processed further in AVAS V4.0A.

CC exit routines

All CC exit routines of Version 3.0A can be taken over into Version 4.0A unchanged.If journal records with four-digit year specifications are needed, the new exit AVEX0002must be used. The fixed part of the journal records must then be defined withVERSION=040 using the AVASJRN macro.

Program interface for BATCH statements

All programs of Version 3.0A can be taken over into Version 4.0A unchanged.Date parameters are still transferred with a two-digit year and must be interpretedcorrectly by the application program. The same applies for the journal records(AVSASSJN macro and COPY element AVSCOBJN).

Note

It is possible to revert from AVAS V4.0A to AVAS V3.0A under the following conditions:

– No new functions of Version 4.0A can be used.

– The Version 3.0A calendar cannot be edited using Version 4.0A. A backup copy ofthe calendar should therefore be made with Version 3.0A.

– No variable standard periods can be set in the period file PERDAT.

It is not possible to revert from AVAS V4.0A to AVAS V2.0A.

U5184-J-Z125-7-76 9

Preface

Compatibility

Nets from Version 3.0A are handled without change under AVAS V4.0A.

All CC exit programs can be transferred unchanged into Version 4.0A.

Journal records that were output to the journal file using Version 3.0A are changed to thenew four-digit year format by the reorganization program during the backup stage.Journal records from Version 3.0A are displayed correctly in Version 4.0A using SHOW-JOURNAL.

A calendar can no longer be edited with AVAS Version 3.0A after the following changes:

– When new calendar sections are created by changing the calendar limit dates (FIRST/LAST-CAL-DATE), these are created in the new format (with the century specified in theday record).

– When a completely new calendar is created, the HEADER record is created in the newformat (with the century and the new record length).

– If the new parameter value NWRK is used for a calendar day or if more than 28 symbolicdates are created.

1.6 Notational conventions

References to other publications are quoted in the text as abbreviated titles. The full title ofeach publication, which is referenced by a number, will be found under “Related publica-tions” opposite the corresponding number. Notes on how to order publications will be foundat the end of this list.

Supplementary items of information appear under the heading Notes.

Examples of runs and procedures are printed in non-proportional font.

Eine Dokuschablone von Frank Flacheneckerby f.f. 1992

U5184-J-Z125-7-76 11

2 Interactive promptingThe mask-driven AVAS dialog system can be started under any BS2000 user ID. Enteringa statement first causes an overview of all referenced objects to be displayed. Thestatement can now be applied to any of these objects. Alternatively, the set of objects to beprocessed can be limited by means of the marking facility. Once a statement has beensuccessfully processed, the user receives an acknowledgment. In the case of invalid inputs,processing errors or unauthorized access attempts, the error is displayed in the messageline. Information on the statement can be obtained by calling help screens.

2.1 Interactive mode with AVAS

The dialog with AVAS is started with the AVS.DIALOG procedure, which is an element oftype J in the SYSPRC.AVAS.040 library. When communicating with the AVAS system, theuser is prompted with masks (see page 14). To sign on to the AVAS system, the signonmask AVS010 is displayed.

2.1.1 Signing on to the AVAS system

Once the dialog procedure has been started, AVAS displays the signon parameter inputmask AVS010 in the user’s interactive task. The user must enter the following signonparameters in the ASV010 mask in order to identify himself or herself as authorized to usethe AVAS system.

AVS010 - Mask for signing on to AVAS

AVAS-USER-ID Input parameter.Name of the AVAS user.

PASSWORD Input parameter.Password of the AVAS user. The input field is blanked out.

AVAS-SYSTEM-ID Input parameter.Name of the AVAS system with which the user wishes to work. Fiveinvalid input attempts mean that the signon operation is aborted witha corresponding message.

12 U5184-J-Z125-7-76

Interactive prompting

NEW-PASSWORD Input parameterNew password of the AVAS user. This parameter should only bespecified if the user’s present password is to be changed. The inputfield is blanked out.

REPEAT-NEW-PASSWORDInput parameterNew password of the AVAS user. This password is only accepted ifthis entry is identical to the password specified under NEW-PASSWORD. The input field is blanked out.

Users can also change their password in the SIGNON mask if they are not authorized touse MODIFY-SYSTEM-PARAMS.

2.1.2 Calling AVAS system statements

Once the user has successfully signed on, the AVS020 mask is displayed with a list of thestatements which the user is authorized to use and execute. If necessary, the user can pageforward or backward in this list with the paging functions.One of the listed statements can be selected by means of the S mark and the EXECUTEoperation or by entering the corresponding statement in the CMD field. In addition,operands of the marked or entered statement can be specified in the OPR field. In this way,the object, element or set to be processed is determined directly.

Note

It is pointless to mark more than one statement, since only the first S mark is processed.

U5184-J-Z125-7-76 13

Interactive prompting

2.1.3 Signing off from the AVAS system

Termination of the AVAS dialog is initiated by means of the END statement.

The END statement can be entered in the CMD field of any AVAS mask, provided a changeof statement is permissible. Otherwise the current processing operation must first be termi-nated by means the RETURN or SAVE operation.

The END statement disconnects the files from the AVAS dialog task and releases allelements locked by the task. END terminates the AVAS dialog. The user is no longer joinedto the AVAS system.

If a user wants to terminate work under the current user name and continue under adifferent user name, he can make use of the SIGNON statement.

The SIGNON statement makes it possible to terminate the current AVAS dialog andimmediately start a new one.Like END, SIGNON initiates termination of the AVAS dialog and clears all connections tothe user.Thereafter, control branches to the AVAS signon procedure. The user is presented theAVAS signon mask to open a new AVAS dialog.

14 U5184-J-Z125-7-76

System masks

2.2 Mask structure and operation

User communication with the AVAS system is mask-driven. There are two kinds of masks:those made available by the system (AVAS system masks) and those which must becreated by the user (user masks). The AVAS system masks are created using IFG.

2.2.1 Structure of AVAS system masks

As a rule, an AVAS system mask is subdivided into four areas:

Description of mask structure using the AVAS signon mask as an example

Information section (AVAS data) Line 1

Processing section (object data) Lines 2 - 21

Control section (operation or statementand operands)

Lines 22 and 23

Message section (AVAS messages) Line 24

AVAS-Vnn.yxmm/AVziii A V A S - S I G N O N ########/########

PLEASE ENTER IDENTIFICATION

AVAS-USER-ID : PASSWORD : AVAS-SYSTEM-ID :

NEW-PASSWORD : REPEAT-NEW-PASSWORD:

CMD: _____________________ OPR: _____________________________________________ ____________________________________________________________________________MSG: ________________________________________________________________________

Informa-tionsection

Control sectn.

Messagesection

Process-ingsection

U5184-J-Z125-7-76 15

System masks

Line 1 contains the information section :

AVAS-Vnn.yxmm/AVziii text ########/########

AVAS-Vnn.yxmm/ AVAS system version, where: nn = main version of the AVAS system y = revision version xmm = version update

AVziii Name of the AVAS system mask, where: z = function group iii = number of the system mask

AVAS-SIGNON Name of the function and designation of the data processed.

########/######## Date/Time of day in the form: dd.mm.yy/hh:mm:ss

Note

Data in columns 1-13 of the first line of the AVAS system masks can be overwritten,since it must be possible to position the cursor there for the hardcopy function.

Lines 2 through 21 contain the processing section :

This is used as an input/output area for function-specific data of the processed objects.This area is structured differently for each individual mask. It consists of text fields andvariable fields. All parameters are displayed and entered in the variable fields.

In the case of overview masks, the names of the selected objects are displayed in thissection. The objects can be marked in this area. The actions of the system are acknowl-edged here.

16 U5184-J-Z125-7-76

System masks

Lines 22 and 23 contain the control section :

CMD:______________________ Input field for the statement name and the operations Length = 22 characters

OPR:_____________ ... Input field for the operands_______________________ ... Two fields with a total length of 129characters. AVAS combines the two fields to form a single continuous string The operands must be entered in the form name1=value1[,name2=value2]..., with the sequence of operands being arbitrary.

Line 24 contains the message section :

MSG:___________________ ... Area for execution, system and error messages. Length = 75 characters.

U5184-J-Z125-7-76 17

Working with masks

2.2.2 Working with masks

By way of the following mask fields, the user enters the statement name of the function, theoperands and - as an alternative to using the function keys - a statement/character for theoperation in the control section of the masks:

CMD field: operation name or character or

statement name of the function

OPR field: operands

In addition to a syntax check, AVAS also checks whether the user is authorized to use thefunction. The mark column enables the user to select statements (statement selectionscreen) or to mark elements for processing and position the work window (processingsection of the mask).

CMD field with operation name or character:

By entering an operation name or character it is possible to control interactive prompting -as an alternative to using the function keys. The operation name can be specified in abbre-viated form to the point where it remains unique. When the operation has been executed, itis deleted in the CMD field and the current statement of the function is displayed

The following operation characters/names are available:

+/- Paging function over two or more work windows when there is more datathan can be displayed in a single mask.+ Page forward by one work window.- Page backward (towards start of listing) by one work window.If paging goes beyond the end or start of data, positioning takes place aswith ++/--.

+n Page forward n lines (1 ≤ n ≤ 9999)+n displays the n-th record following the first record in the first line of thework window as the first record of the new work window. If this goes beyondthe end of data, positioning takes place as with ++.

++ Positions to end of data. The last record stands in the last line of the workwindow.

LAST Positions to end of data, like ++.

-n Page backward n lines (toward start of data) (1 ≤ n ≤ 9999)-n displays the n-th record preceding the first record in the first line of thework window as the first record of the new work window. If this goes beyondthe start of data, the display is positioned to the first record.

-- Positions to start of data. The first record stands in the first line of the workwindow.

18 U5184-J-Z125-7-76

Working with masks

FIRST Positions to start of data, like --.

? Branch to the information functions assigned to the current statement. If asystem mask of the statement has already been displayed, the informationis specific to the fields of this mask.

RETURN 1) Abort element processing.2) Return from the information function.

EXECUTE Execute the statement immediately; start element processing.EXECUTE must be entered by the user.

PRINT Output to a SAM fileOutput listings for documentation purposes in connection with the state-ments SHOW-NET-DESC, CREATE-PLAN-NET, SHOW-PLAN-NET,SHOW-DOCUMENT, SHOW-JOB, SHOW-PROD-JOB, SHOW-JOB-LOG,SHOW-NET-STATUS and SHOW-JOURNAL.PRINT must be entered by the user (see also page 24).

DOCUMENT Displays the documentation element, that is assigned to the currentelement, with the following statements:SHOW-NET-DESCRIPTION, SHOW-NET-STATUS and RESTART-NET

With the CREATE-NET-DESCRIPTION and MODIFY-NET-DESCRIPTIONstatements, a branch occurs to processing of the documentation elements.

CHECK Calls up the CHECK function. This operation can only be specified in masksthat are called up by the statements CREATE-NET-DESCRIPTION,MODIFY-NET-DESCRIPTION and MODIFY-SUBMIT-NET.Depending on the result of the checks, an appropriate message is output inthe mask on completion of the CHECK operation.

JOBLOG Displays the runtime logs for a job. The operation may only be specified inthose masks called by the statements SHOW-NET-STATUS and SHOW-JOURNAL.Depending on the current statement and mask, the logs are displayed oncompletion of the JOBLOG operation.

If an EDT procedure was preset by the AVAS administrator , the user canstart this procedure using the statement @do n (n = number of the workfile tobe queried with the AVAS administrator).

CONTINUE Causes a change of mask within an object description when data must beentered or displayed for these objects over more than one mask. Dataentered via the existing mask is saved.

IGNORE Same as CONTINUE, but the entered data is not saved.

SAVE A processed object is stored in the file associated with the object or in thespecified file.

U5184-J-Z125-7-76 19

Working with masks

Note

All operations can - as an alternative to entry in the CMD field - be entered via functionkeys. The assignment of function keys to the operations is made through the AVASgeneration parameters.All operation names can be specified in abbreviated form to the point where they remainunique. The statement overwritten by the operation in the CMD field need not becleared. However, the operation must be terminated by at least one blank. Afterexecution of the operation, the overwritten statement in the CMD field is displayed in itsentirety.

Positioning the work window with marks + and –

Entering + or - in the mark column positions the work window to the marked line.

+ A + in the mark column of a line positions the work window so that themarked record appears as the first record in the work window.Only one line may be marked with +. There must be no - mark in the samework window.

If the operation character + or - is specified in the CMD field, the positionselected by the mark + in the work window will be the active position.If ++ or -- is specified in the CMD field, a mark + will be ignored.

- A - in the mark column of a line positions the work window so that themarked record appears as the last record in the work window.Only one line may be marked with -. There must be no + mark in the samework window.In the first work window (start of data), the - mark has no effect.

If the operation character + or - is specified in the CMD field, the positionselected by the mark - in the work window will be the active position.If ++ or -- is specified in the CMD field, a mark will be ignored.

20 U5184-J-Z125-7-76

Working with masks

CMD field with statement name of function:

The name of a statement is composed of two or more name parts connected by hyphens.The name may be entered complete or with abbreviated name parts, provided the nameparts can be identified uniquely.

For interactive prompting purposes, input of a modified statement name takes precedenceover all other inputs. This means that a new statement name interrupts current statementprocessing, provided that a change of statements is permissible.If the CMD field is cleared, the most recent valid statement is entered here. An overview ofstatements is obtained by entering CMD:??.

If a statement from the overview of statements is marked, the operands valid for the previ-ously active statement can be taken over and used again. If this is not desired or if theoperands are not permissible for this statement, the operands must be deleted.

OPR field:

The operands have the following format:

operand-name-1=operand-value[,operand-name-2=operand-value,...]

The sequence of operands is arbitrary. These are keyword operands.

The operand names are governed by the same abbreviation rules as the statement names.Operand values must not be abbreviated; they must always be specified in full, even in thecase of keyword operands.

If the CMD or OPR field is updated, no parameters are taken over from the current mask.

Specification of the RUN-CONTROL-SYSTEM operand is omitted if the requestedstatement does not permit this operand. In any subsequent statement which requires theRUN-CONTROL-SYSTEM operand, the default value is assumed if the operand is notdefined.The same applies to the NET-STATUS and CANCEL-TYPE operands.

U5184-J-Z125-7-76 21

Working with masks

Selecting statements and elements

Once the user has successfully signed on to AVAS, the system displays a list of statementswhich he is allowed to work with. By using the paging functions +/-/FIRST/LAST (seepage 17) he can scan the entire list of statements.

The user can select statements either by entering an S in the mark column and theEXECUTE operation, or by entering the statement name in the CMD field and the relevantoperands in the OPR field. The statements are used for processing elements from AVASlibraries and files.

Entering S in the mark column together with the ? operation causes (help) information to bedisplayed for the marked statement.

If the user has specified a fully qualified element name, the element will be processeddirectly.

If he has specified a partially qualified element name as an operand, he will receive anoverview mask with a list of elements relevant to his purposes. Using this list, he can thenselect the elements he wishes to process by marking them with S, Y or N.

– Selecting elements by entering S in the mark column and starting element processingwith the EXECUTE operation:

The S mark means that an element can still be modified before the statement isexecuted (except for SHOW ... statements). S always causes a new mask to bedisplayed (e.g. MODIFY-NET-DESCRIPTION).

– Selecting elements by entering Y or N in the mark column and starting elementprocessing with the EXECUTE operation:

Unlike S, the marks Y (process marked elements) and N (exclude marked elementsfrom processing) mean that an element no longer needs to be modified before thestatement is executed (e.g. COPY-NET-DESC).

Only S or Y or N can be entered as a mark for selecting elements. A mixture of marksis not permitted. With some statements, marks A and D can be used to add or deleteinformation.

22 U5184-J-Z125-7-76

Working with masks

S mark

The first element selected via S is presented on the screen for processing.

Once the user has processed the element, he can continue as follows:

– Write the element to the file/library with the SAVE operation, or abort processing withthe RETURN operation.

If the write operation cannot be performed correctly, a corresponding message isdisplayed in the message line and the immediately preceding screen is displayed again.SAVE can be entered after the required correction has been made.

If he aborts element processing with RETURN, the next element is presented forprocessing.

Once element processing has been started by means of EXECUTE, all markedelements are processed in a cycle. Following the final element, the overview screen isredisplayed. The marks for the processed elements are erased and the result is enteredin the RESULT column. To save the result, SAVE must be entered.

The user can start the same statement again by repeating the mark and entering theEXECUTE operation. Alternatively, he can change statements by specifying a newstatement name in the CMD field and entering the corresponding operands.

– If it is possible to process an element via two or more masks (e.g. in the case of CREA-NET-DESC), the user can have the next screen displayed by means of the CONTINUEoperation.

Element processing is completed by entering SAVE or RETURN.

SAVE means that the element is written to the file/library.

RETURN means that element processing is aborted without a write operation.

Y mark

Elements marked with Y are processed from the overview mask. The result is entered inthe RESULT column.

If all elements have been processed in sequence, or even if an element could not beprocessed correctly, a corresponding result is displayed in the RESULT column. No SAVEoperation is required to save the results. Elements which it has been possible to processcorrectly are written, after the processing, into the assigned library/file.

U5184-J-Z125-7-76 23

Working with masks

N mark

An N mark means that all elements will be processed except those marked with N. If noelements are marked, this means that all elements will be processed (i.e. no elements areexcluded by means of N).

The N mark is prohibited in conjunction with the DEL... statements so as to preventinadvertent deletion.

If other marks are used for a particular function, this is indicated in the description of thestatement.

Example: Using masks with CREATE/MODIFY-NET-DESCRIPTION

Element processing entries are made via masks AVN001, AVN020, AVN006 and AVN004.You can move to the next mask by entering CONTINUE or by changing the operand valueof OBJECT.

With CREA/MOD-NET-DESC, the CONTINUE operation is prohibited in mask AVN004.However, you can switch to mask AVN001, AVN020 or AVN006 via the OBJECT operand.If JOB or COND control records are marked in mask AVN004, you can start processingthem by entering the EXECUTE operation.

If the marks in a mask caused further masks to be displayed at the next level (e.g. AVN004→ AVN002/AVN003), the user must return to the calling level via the CONTINUE orIGNORE operation before the element can be written with SAVE.

CONTINUE means that the entries made via the mask are included and the next elementcontrol record is displayed.IGNORE means that the entries made via the mask are not included and the next elementcontrol record is displayed.

If the user enters the RETURN operation in mask AVN002/AVN003, element processing isaborted and the overview mask is redisplayed.

With CREA-NET-DESC, the user can also abort element processing in mask AVN001/AVN020/AVN006/AVN004. The overview mask is then redisplayed.

24 U5184-J-Z125-7-76

AVS015 mask Working with masks

Using the PRINT operation

The user can specify the PRINT operation only in those masks which are called by thefollowing statements:

CREATE-PLAN-NET, SHOW-PLAN-NET, SHOW-NET-DESCRIPTION, SHOW-DOCUMENT, SHOW-JOB, SHOW-PROD-JOB, SHOW-JOB-LOG, SHOW-NET-STATUSand SHOW-JOURNAL.

Following CMD:PRINT, AVAS displays the mask AVS015 with the name of the SAM file forlist output. When the print function is called for the first time, either the default name in theform LST.AVAS.ug.avuser.yyyymmdd.hhmmss or the file name defined via the BS2000 command/SET-FILE-LINK LINK=AVASPRT,FILE-NAME=filename is output in the parameter field LIST-FILE-NAME. This name can be changed (see the naming conventions from page 42). Onfurther calls with PRINT, AVAS provides the last name entered. If the name is not changed,it is retained for the next output.

Note

The messages from the CHECK functions are likewise output to the currently assignedPRINT file (see CHECK operation).

The EXECUTE operation starts the output under the specified file name, and processing isresumed.

If the user wishes to abort the print function, he must specify the RETURN operation in theCMD field of mask AVS015. The mask for the previous processing operation is displayed.

AVS015 - Mask for entry of print parameters

LIST-FILE-NAME Input/output parameterName of a SAM file.The displayed name of this output file can be overwritten, ifnecessary.Standard name: LST.AVAS.ug.avuser.yyyymmdd.hhmmss

EXTEND Input/output parameter{YES | NO}

YES An existing output file is to be extended or a new file created.

NO A new output file is to be created.If a file having the same name already exists, it will be overwritten(OVERWRITE=YES).

U5184-J-Z125-7-76 25

Working with masks

Using the DOCUMENT operation

The user may only specify the DOCUMENT operation in the masks called by the statementsin the table below.

With all other statements and on the element overviews of the specified statements entryof the DOCUMENT operation is rejected.

After the DOCUMENT operation, depending on the current statement and mask, thefollowing documents are displayed via EDT:

Statement Mask Documentation file DOCUMENT operation

CREATE-NET-DESCR AVN001AVN002AVN003AVN004AVN006AVN008AVN009AVN020AVN021AVN022AVN023AVN024AVN030AVN031AVN032

NET-DOCJOB-DOCCOND-DOCNET-DOCNET-DOCCOND-DOCJOB-DOCNET-DOCJOB-DOCCOND-DOCCOND-DOCCOND-DOCCOND-DOCCOND-DOCCOND-DOC

processprocessprocessprocessprocessprocessprocessprocessprocessprocessprocessprocessprocessprocessprocess

MODIFY-NET-DESCRotherwise seeCREATE-NET-DESCR

AVN011 - - - invalid

ADD-COND-DESCR AVD040AVD030

- - -COND-DOC

invalidprocess

MODIFY-COND-DESCR AVD040AVD030AVD031

- - -COND-DOC- - -

invalidprocessinvalid

SHOW-COND-DESCR AVD040AVD030AVD031

- - -COND-DOC- - -

invaliddisplayinvalid

26 U5184-J-Z125-7-76

Working with masks

Masks AVN001, AVN002, AVN003, AVN008, AVN009, AVN030, AVN031, AVN032 andAVD030 are output via the statements CREATE-NET-DESCRIPTION, MODIFY-NET-DESCRIPTION, ADD-CONDITION-DESCRIPTION and MODIFY-CONDITION-DESCRIPTION. The documentation files can be assigned to the nets, to the individualstructure elements in a net and to the condition specifications via of the parameter fieldscontained in the masks:

NET-DOC mask AVN001

JOB-DOC mask AVN002, AVN009

COND-DOC masks AVN003, AVN008, AVN030, AVN031, AVN032mask AVD030

SHOW-NET-DESCR AVN011AVN001AVN002AVN003AVN004AVN006AVN008AVN009AVN020AVN021AVN022AVN023AVN024AVN030AVN031AVN032

---NET-DOCJOB-DOCCOND-DOCNET-DOCNET-DOCCOND-DOCJOB-DOCNET-DOCJOB-DOCCOND-DOCCOND-DOCCOND-DOCCOND-DOCCOND-DOCCOND-DOC

invaliddisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplay

SHOW-NET-STATUS AVI012AVI002AVI003AVI004AVI007AVI008AVI009AVI010AVI013AVI020

---NET-DOCJOB-DOCCOND-DOCCOND-DOCCOND-DOCCOND-DOCCOND-DOCNET-DOCJOB-DOC

invaliddisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplaydisplay

RESTART-NET AVD012AVD007AVD005

- - -NET-DOCJOB-DOCCOND-DOC

invaliddisplaydisplay

Statement Mask Documentation file DOCUMENT operation

U5184-J-Z125-7-76 27

Working with masks

The following entries are permitted in the parameter fields (see the CREATE-NET-DESCRIPTION statement):

{*STD | element | *NONE}

*STD The documentation is sought or stored under the standard nameDOCLIB, where:

NET-DOC : $ugnet_netnameJOB-DOC : $ugnet_netname.jobnameCOND-DOC : $ugnet_netname.condname

Note that with the netname_yymmdd[_hhmmss] form of the NETcondition, no documentation element can be referenced via *STD.An element name must be given here.

element Element name for the documentation of the net in the DOCLIB orDOCSYS.$ugnet_docname$ugsys_docnamedocname

The maximum length of docname is 37 characters. If no user groupis specified, the documentation is sought in the DOCLIB under theuser group of the net. If $ugsys is specified, the documentation issought in the DOCSYS.

*NONE No documentation is used.If the DOCUMENT operation is entered for the net, a job or acondition of the net, the following message is output:AVS4090 THE DOCUMENT FUNCTION IS NOT AVAILABLE

The documentation elements are processed using the EDIT-DOCUMENT statement (seefrom page 106) or through the DOCUMENT operation in the case of the CREATE/MODIFY-NET-DESCRIPTION statements (see above).Processing using EDIT-DOCUMENT has no influence of the assignment of the documen-tation elements to the nets. The assignment is made only via the name specified in the netor the standard name assumed with *STD.When the documentation elements are processed by the DOCUMENT operation within theCREATE/MODIFY-NET-DESCRIPTION statements, the name of the documentationelement can be modified. After returning from EDT, another name can be entered in theNEW-ELEMENT-NAME field of the AVS016 mask.The DOCUMENT operation can only be used to process (overwrite) those elements wherethe user group of the documentation element is the same as the user group of the net.Documentation elements of a different user group can be used as input elements (readaccess) but may not be overwritten. The entry of NEW-DOCUMENT-NAME is expected,where only the user group of the net is permitted.

28 U5184-J-Z125-7-76

Working with masks

Documentation elements with the system user group occur when they are transferred to theDOCSYS by means of the COPY-SYSTEM-ELEMENT statement.

Using the CHECK operation

The user may only specify the CHECK operation in those masks called by the followingstatements:

CREATE-NET-DESCRIPTION, MODIFY-NET-DESCRIPTION and MODIFY-SUBMIT-NET

The CHECK operation is rejected when specified by any other statement.

Depending on the result of the checks, an appropriate message is output in the mask oncompletion of the CHECK operation.Messages from CHECK are spooled to the associated PRINT file (see the PRINToperation, mask AVS015, parameter LIST-FILE-NAME).

Statement Mask CHECK operation

CREATE-NET-DESCRIPTION AVN001AVN002AVN003AVN004AVN006AVN008AVN009AVN020AVN021AVN022AVN023AVN024AVN030AVN031AVN032

validinvalidinvalidvalidvalidinvalidinvalidvalidinvalidinvalidinvalidinvalidinvalidinvalidinvalid

MODIFY-NET-DESCRIPTIONotherwise as forCREATE-NET-DESCRIPTION

AVN011 invalid

MODIFY-SUBMIT-NET AVD011AVD001AVD002AVD003AVD004AVD009AVD010AVD016AVD017AVD018

invalidvalidinvalidinvalidvalidinvalidinvalidinvalidinvalidinvalid

U5184-J-Z125-7-76 29

Working with masks

Notes

– The CHECK operation is rejected on the element overviews of the valid statements.

– The CHECK operation is not allowed in the following parameter masks for structureelements:AVN002, AVN003, AVN008, AVN009, AVN021, AVN022, AVN023, AVN024, AVN030,AVN031, AVN032 and AVD002, AVD003, AVD009, AVD010, AVD016, AVD017 andAVD018.

The current entries in these masks are not accessible to CHECK until after theCONTINUE operation.

CHECK in conjunction with the SAVE or EXECUTE operations

The statements CREATE/MODIFY-NET-DESCRIPTION, MODIFY-SUBMIT-NET andCOPY-ELEMENT (with MODE=LIBIN/SAMIN and AVAS-USER-LIB=NETLIB) performinternal calls to the CHECK function in the SAVE and EXECUTE operations.

Messages from CHECK are output to the currently assigned PRINT file (see PRINToperation).

Statement Mask CHECK and SAVE operations

CREATE-NET-DESCRIPTION AVN001AVN004AVN006AVN020

CHECK is calledCHECK is calledCHECK is calledCHECK is called

MODIFY-NET-DESCRIPTION AVN001AVN004AVN006AVN020

CHECK is calledCHECK is calledCHECK is calledCHECK is called

MODIFY-SUBMIT-NET AVD001AVD004

CHECK is calledCHECK is called

CHECK with the EXECUTE operation

COPY-ELEMENT withMODE=LIBIN/SAMINAVAS-USER-LIB=NETLIB

AVS011 CHECK is called for all netsthat are to be copied.

30 U5184-J-Z125-7-76

Working with masks

Notes

– MODIFY-NET-DESCRIPTION and MODIFY-SUBMIT-NET statements:

– Overview processing with S markNets in which errors (warnings) have been detected are written back and displayedin the AVN011 or AVD011 masks with the result WARNING.

– Processing of single statements with fully qualified net namesNets in which errors (warnings) have been detected are written back and a warningmessage displayed in the AVS030 mask.

– COPY-ELEMENT statement:If CHECK creates an error log, a message containing the LIST-FILE-NAME is output(BATCH only).Nets that were not copied because of serious errors are displayed in the AVS011 maskwith the result ERROR.Nets that were copied despite containing errors are displayed in the AVS011 mask withthe result WARNING.

Information function

The user calls the information function by means of the operation character ?. The calledfunction always refers to the statement specified in the CMD field. In response to ? the useris given information functions specific to the mask involved. The user can page back andforth over two or more screens within the information function by means of the operationcharacters + and –.

Entering the RETURN operation returns the user to the processing level.

U5184-J-Z125-7-76 31

Working with masks

Overview of the operation names, characters and marks

Operation names and characters

Note

Paging may cause output of the following messages:

MSG:5070 END OF DATA REACHED

The last record/element is displayed in the work window.

MSG:5071 START OF DATA REACHED

The first record/element is displayed in the work window.

If positioning to the start/end of data is performed explicitly by means of the FIRST,– –, LAST or ++ operations, these messages are not output.

CMD: Paging

FIRST from first page

– – from first page

– one page back

–n n records toward start of data (1 Î n Î 9999)

+ one page forward

+n n records toward end of data (1 Î n Î 9999)

++ last page

LAST last page

CMD: Element processing

EXECUTE Start element processing from element overview(process marks)

SAVE Store element

RETURN Abort element processing

32 U5184-J-Z125-7-76

Working with masks

CMD: Records of an element

EXECUTE Start record processing from record overview(process marks)

CONTINUE Display next record (mask), store data.(with SHOW functions no data is stored)

IGNORE Next record, do not store data

CMD: Miscellaneous

PRINT Output data in accordance with mask in LIST-FILE or default list

DOCUMENT Display assigned documentation element

CHECK Call CHECK-NET functions

JOBLOG Display a runtime log

? Call information function: information on statement in CMD field

?? Overview display of statements

U5184-J-Z125-7-76 33

Working with masks

Marks

Positioning the work window

+ : The marked line is the first record in the work window

– : The marked line is the last record in the work window

Element selection

a) With SHOW, MODIFY, COPY and CREATE statements:

S : The marked element is presented for processing (with EXECUTE).

Y : The marked element is processed as per the statement (with EXECUTE).

N : The marked element is not processed (with EXECUTE).

b) With DELETE statements:

Y : The marked element is deleted (with EXECUTE) - RESULT=DELETED.

Selecting records

S : The record is presented for modification.

Y : The record is processed as per the statement.

N : The record is not processed.

Deleting and adding a record

D : The record is deleted.

A : The record is added.

Processing a symbolic date (SYMDAT) of a record in conjunction with the calendarstatement MODIFY-CALENDAR.

A : The SYMDAT specified as an operand is added to the record.

D : The SYMDAT specified as an operand is deleted from the record.t

Notes

– If a fully qualified element name is specified as the operand of a statement, elementprocessing (editing) is started without EXECUTE.

– IGNORE and CONTINUE have no effect in masks containing record overviews.

34 U5184-J-Z125-7-76

General description of masks AVAS-DOORS

2.3 AVAS-DOORS - graphic interface for AVAS

AVAS-DOORS is not actually an application, but consists of around 100 mask descriptionfiles (one for every AVAS mask). FHS-DOORS uses these AVAS-DOORS masks toreproduce the AVAS masks graphically. When FHS-DOORS is started, a session isopened, and a connection to AVAS is set up on the BS2000 host; then the AVAS-DOORSmasks are automatically loaded and displayed.

AVAS-DOORS provides users with a graphic interface for AVAS in BS2000 under FHS-DOORS. All alphanumeric FHS masks in AVAS were converted for this purpose to graphicAVAS-DOORS masks and were then optimized further so that they are easier to use andmake better use of the advantages of graphic interfaces. However, the AVAS-DOORSmasks were only changed to such an extent that the AVAS masks can still be recognizedand even experienced AVAS users have no difficulty upgrading.

General description of the AVAS-DOORS masks

The AVAS masks were converted using the FHS-DOORS mask converter. The convertedmasks were then optimized and additional graphic operating elements were added to makethem even easier to use. The optimizations are described here using the example of theAVC012 mask.

Figure 1: AVAS mask AVC012 in BS2000

U5184-J-Z125-7-76 35

AVAS-DOORS General description of masks

Figure 2: AVAS-DOORS mask AVC012 under FHS-DOORS

The size of all AVAS-DOORS masks was increased to 800 x 600 pixels. This makes iteasier to show large amounts of information in a mask more clearly and to integrateadditional operating elements in the masks. A resolution of 800 x 600 pixels is recom-mended for displaying complete masks.

Working with AVAS-DOORS masks is the same as working with AVAS masks. However,some operating elements are new and these are explained in the next sections.

Single selection buttons (e.g. mark column)

Fields with few alternative options for selection (e.g. the mark column) have been replacedby a group of single selection buttons. By clicking on a single selection button you selectthis option and enter the relevant value in the field. The individual values are shown in theheading above each of the single selection buttons. The single selection button to theextreme right corresponds to the value “Ë“ (blank), i.e. no value has been selected for thisfield. “Ë“ is the default value. If you want to cancel a value selected for a field, click on thesingle selection button “Ë“.

When masks are used a number of times, it may happen that values that are not permittedare also selected in the current dialog situation. Please refer to the descriptions of themasks in the AVAS manuals to find out which values can be used in each of the masks.

36 U5184-J-Z125-7-76


Multiple selection buttons

Fields with just two alternative options for selection (e.g. the field OVERWRITE=YES | NO)have been replaced by a multiple selection button. By clicking on a multiple selection buttonyou activate or deactivate the multiple selection button. A ticked multiple selection buttoncorresponds to the value YES. A multiple selection button that is not ticked corresponds tothe value NO. Please refer to the descriptions of the masks in the AVAS manuals to find outthe preset values in each of the masks.

Buttons

Frequently used commands have been mapped to buttons. Clicking on a button executesthe corresponding command. The command shown on the button is automatically writteninto the CMD: field and the [DUE1] key is then activated. The only exception is the

button. When you click on , only the [DUE1] key is activated.

Instead of clicking on a button, you can also enter the command manually in the CMD: fieldand then press the key for [DUE1].

Button Command

[DUE1]

EXECUTE [DUE1]

CONTINUE [DUE1]

SAVE [DUE1]

RETURN [DUE1]

IGNORE [DUE1]

CHECK [DUE1]

PRINT [DUE1]

DOCUMENT [DUE1]

JOBLOG [DUE1]

+ [DUE1]

– [DUE1]

++ [DUE1]

– – [DUE1]

OK OK

OK

EXECUTE

CONTINUE

SAVE

RETURN

IGNORE

CHECK

PRINT

DOCUMENT

JOBLOG

+

–

+ +

– –

U5184-J-Z125-7-76 37


User-defined masks

AVAS-DOORS does not contain any user-defined masks. If a user-defined mask is calledunder FHS-DOORS, the mask is converted using the FHS-DOORS “Automask“mechanism. In this way it is possible to use the advantages of graphic masks even for user-defined masks. However, the masks that are converted by Automask are not optimized, i.e.they do not include any of the improvements described in the previous section. If you alsowant to optimize user-defined masks, you must first convert the masks using the FHS-DOORS mask converter, and then postprocess them using the Dialog Builder. For adescription of this, refer to the manual “FHS-DOORS, Mask Conversion and Optimization“[13].

Calling EDT

The EDT work window is not interpreted by FHS-DOORS. If EDT is called within AVAS, theprogram switches to the emulation window and EDT is displayed unchanged.

If the DOORS Mini-Emulation is used for the connection to the BS2000 host, the programbranches to the Line mode when EDT is called.

Increasing and reducing the size of AVAS-DOORS masks

The AVAS-DOORS masks can be resized as required, but the absolute size of the font andthe fields always remains the same. A proportional increase or reduction in size is notpossible. However, you can change the font using the FHS-DOORS function Setup: Font.

If the window is reduced to less than 800 x 600 pixels, it is no longer possible to display thecomplete mask. Scroll bars then appear in the window. These scroll bars allow you to movethe mask around within the window in order to display hidden areas of the mask.

If the window is increased to a size greater than 800 x 600 pixels, the part of the windowthat is not needed to display the mask always remains blank.

Starting and terminating AVAS-DOORS

Starting AVAS-DOORS

The easiest way to start AVAS-DOORS is the direct start. This involves creating an AVAS-DOORS icon in the Microsoft Windows Program Manager (see the section describing howto create an AVAS-DOORS icon in “AVAS for the Administrator“ [3]). You can then startAVAS-DOORS by double-clicking on this AVAS-DOORS icon.

38 U5184-J-Z125-7-76


If you want to start AVAS-DOORS without an icon, and you do not have an existing AVAS-DOORS session stored in memory, you must complete the following steps:

Ê Start FHS-DOORS by double-clicking on the FHS-DOORS icon.

Ê Select the function Session: New... The New Session dialog box opens.

Ê From the Resource Path list, select the directory in which the AVAS-DOORS masks arestored (e.g. C:\AVSDOORS).

Ê Enter the following in the emulation parameters input fields:

Filename: File name of the terminal emulation used,e.g. C:\FHSDOORS\DOORS_EM\DOORS_EM.EXE

Parameters: Parameters for the terminal emulation, or the file name of theparameter file created for the terminal emulation,e.g. C:\FHSDOORS\DOORS_EM\AVASD.DRE

Ê Click on the button to start the AVAS-DOORS session.

Ê Switch to the emulation window and start AVAS in the usual way (e.g. call the LOGONprocedure for starting the AVAS dialog).

Further information on sessions, e.g. how to open a new session, how to edit and save thecurrent session and how to open a saved session, can be found in the manual“FHS-DOORS“ [14].

Terminating AVAS-DOORS

Ê Select the function Session: Exitin order to terminate FHS-DOORS and alsoAVAS-DOORS.

Start

U5184-J-Z125-7-76 39


Example

The following example shows how to select structure elements of an AVAS net using AVAS-DOORS.All manual entries are printed in lowercase letters.

Ê Enter the signon data and click on .OK

40 U5184-J-Z125-7-76


Ê Select SHOW-NET-DESRIPTION and click on .

Ê Select the net, enter “str” for OBJ and click on .

EXECUTE

EXECUTE

U5184-J-Z125-7-76 41


You can select the desired structure elements using the single selection buttons in the markcolumn. To do this, click on .EXECUTE

42 U5184-J-Z125-7-76

Naming conventions

2.4 Naming conventions

Naming conventions and maximum name lengths are governed by the following rules:

The maximum name lengths are determined by the type of storage and planned processinginvolved.

For PLAM libraries: max. length = 64 bytes (element names)

For ENTER calls: max. length = 38 bytes (file name + element name)

Name format of elements in the PLAM libraries:

Overview of names and name parts, together with their lengths:

NETLIB: $ug_netname max.length = 18 bytes

NETSYS: $ugsys_netname max.length = 18 bytes

JCLLIB: $ug_jobname max.length = 30 bytes

JCLSYS: $ugsys_jobname max.length = 30 bytes

DOCLIB: $ug_docname max.length = 43 bytes

DOCSYS: $ugsys_docname max.length = 43 bytes

NPRLIB: $ug_netname_yymmdd_hhmmss max.length = 32 bytes

JMDLIB: $ug_jobname[_netname[_yymmdd_hhmmss[_index]]] max.length = 57 bytes

JMDSYS: $ugsys_jobname[_netname] max.length = 43 bytes

CALLIB: calendar max.length = 20 bytes

NETMAP: format max.length = 8 bytes

JOBMAP: format max.length = 8 bytes

LOGSYS: $ug_netname_yymmdd_hhmmss_catid_tsn_yyyymmdd max.length = 51 bytes(S portion)

$ug_netname_yymmdd_hhmmss_catid_tsn_yyyyymmdd_nn max.length = 54 bytes(D portion)

Name Lengthin bytes

Meaning

calendar 1-20 Name of a calendar

format 1-8 Name of a user mask

U5184-J-Z125-7-76 43

Naming conventions

Notes

– AVAS data subject to BS2000 conventions (e.g. FILE-NAME, NET-USER, NET-ACCOUNT etc.) is not checked by AVAS.

– The characters @, - and _ must not be used for the names of the AVAS elements in thejob and net libraries, in the calendar library and in the period file. These characters areAVAS delimiters and are reserved for identifying parts of the names.

Name part Lengthin bytes

Meaning

$ 1

ug | ugsys 1-4 Name of the user group / system user group

_ 1

jobname | condname 1-24 Name of a job or a condition description

_ 1

netname 1-12 Name of a net

_ 1

docname

_

1-37

1

Name of a documentation elementStandard names:NET-DOC: netnameJOB-DOC: netname.jobnameCOND-DOC: netname.condname

yymmdd 6 (fixed) Date specification: <year> <month> <day>

_ 1

hhmmss 6 (fixed) Time of day: <hours> <minutes> <seconds>

_ 1

catid 1-4 Name of a catalog identifier

_ 1

tsn 4 (fixed) Task sequence number

_ 1

yyyymmdd 8 (fixed) Processing date: <year> <month> <day>

_ 1

nn 2 (fixed) Sequence number

44 U5184-J-Z125-7-76

Naming conventions

– The digits 0 through 9 are not permitted as the first character of a name.

The character $ may only be used as the first character for the following names:

CALENDAR-NAME, SYMDAT-NAME, PERIOD-NAME, CONDITION-JVA-NAME,RUN-CONTROL-SYSTEM and FORMAT-NAME.

– For the names of the server jobs, the same rules apply as for BS2000 jobs if theelements are stored in AVAS libraries. Names which do not follow these conventionscan only be specified for external jobs.

Periods (i.e. periods of time within the calendar) are stored in the ISAM file PERDAT.

Note

The same rules that apply to the elements in the AVAS libraries also apply to the namesof the periods in the period file.

The names must not contain special characters - these are also illegal in libraryelements. The reserved characters @, - and _ as well as the digits 0 through 9 must notbe used as the first character of the period name. $ can be used as the first character.

Name Lengthin bytes

Meaning

period 1-20 Symbolic name of a period (time interval).

U5184-J-Z125-7-76 45

Naming conventions

2.4.1 Entry of partially qualified element names

Users entering partially qualified element names receive an overview of all elements in theassigned AVAS file which have been defined by a partially qualified name.

The following partially qualified names are permissible:

– Element names consisting of parts of names separated by "_" (underscore) can bespecified up to and including "_". AVAS adds an asterisk to this partial qualification.

[$ug_]jobname_[netname_[yymmdd_[hhmmss]]][$ug_]netname_[yymmdd_[hhmmss]]

Partial qualification using "." (period) is not permissible.

– Element names can be shortened as desired by using "*" (asterisk). The "*" replacesany string which follows it.

Examples

NET-NAME=$UGR1_FI*All nets of user group $UGR1 which begin with the string FI areselected.

NET-NAME=FI* All nets of the user’s own user group which begin with the string F1are selected.

NET-NAME=$A* All nets of all user groups which begin with the string $A areselected.

Keywords, names of run control systems (avak), and the system user group $ugsys cannotbe specified as partially qualified names.

46 U5184-J-Z125-7-76

Naming conventions

2.4.2 Wildcards in user groups and element names

The user group and the remainder of element names must be regarded separately whenentering wildcards. This means that the maximum length of the user group cannot beexceeded. The entire wildcard term cannot be longer than the maximum length of therelevant element name.

Wildcards cannot be entered for a calendar name, period name or format name.Likewise, the entry of wildcards is also prohibited for accessing AVAS-external libraries/files(COPY-ELEMENT statement with MODE= LIBIN,ELEMENT/GROUP=) and conditionentries in the run control file (SHOW-/ MODIFY-COND-DESCRIPTION).

Notes – Given the length restriction, it does not make sense to specify wildcards forthe user group in angle brackets.

– The BS2000 wildcard syntax is described in detail in the “Commands“ [7]manuals.

Wildcard Meaning

*

/

<wildcard1, ... >

<wildcard1, wildcard2>

<wildcard1: wildcard2>

Replaces any character string, even a blank character string.

Replaces any one character.

Replaces all character strings to which one of the specified wildcardsapplies.

Replaces a character string that meets the following criteria:– it is at least as long as the shortest wildcard character string– it is not any longer than the longest wildcard character string– it comes between wildcard1 and wildcard2 when sorted alphabeti-

cally; numbers are sorted after letters– wildcard1 can also be the blank character string that comes first

when sorted alphabetically.

Wildcards of type <wildcard1:wildcard2> can also be specified as a list.Every extent specification of this kind is governed by the above rules.The system implements a logical OR link, i.e. the wildcard list replacesall character strings to which one of the extent specifications applies.The length attributes apply in pairs, i.e. for each extent specification, notfor the entire list.

U5184-J-Z125-7-76 47

Naming conventions

2.4.3 Syntax description:

The following metacharacters are used for the syntactic representation of the statementsand their operands:

Notation Explanation Examples

UPPERCASELETTERS andspecial characters

Uppercase letters and special charactersdenote constants, which must beentered by the user in precisely this form.

NETNAME=$XYZ_NET.X

NETNAME=$ug_netname

Enter:NETNAME=$ABCD_NET1

lowercase letters Lowercase letters denote variables, forwhich the user must substitute currentvalues upon input.

{ } Braces enclose alternatives, i.e. one ofthe entries must be chosen. The alterna-tives are separated from each other byvertical bars.

OBJECT={NET | MAP | STR}

Enter:OBJECT=NET orOBJECT=MAP orOBJECT=STR

[ ] Square brackets enclose optionalentries.

[$ug_]netname

Enter:$ABCD_NET1 or NET1

Underscore Underscoring serves to denote defaultvalues. These are the values adopted byAVAS when the user fails to make anentry.

{NET | MAP | STR}

Enter:NET or MAP or STRornothing (is the same asentering NET)


U5184-J-Z125-7-76 49

User masks

3 Creating jobs/S procedures/server jobs,documentation elements and netsTasks (jobs, S procedures, server jobs) and JCL elements are created or edited by meansof the EDIT-JOB statement. Jobs, server jobs (SV jobs) and S procedures which havealready been created and are executable in BS2000 or in a server system can be includedin the AVAS environment (see the COPY-ELEMENT statement on page 207).AVAS statements and variables can be incorporated into any jobs, S procedures, SV jobsand JCL elements. They enable the user to encode in the individual job, SV job, JCLelement or S procedure, those values which vary from run to run, thereby making themeasier to modify. Within the framework of job modification, these encoded values are thenconverted with the aid of user masks and the USER-PARAM-FILE into current values andincorporated into the jobs. In the case of SV jobs and S procedures, the encoded valuesare assigned the current values and are stored in the parameter area.

Besides the BS2000 jobs started from AVAS through ENTER-JOB, SV jobs executed viathe AVAS-SV server are also possible.S procedures are started by AVAS via the ENTER-PROCEDURE call.S procedures are procedures that conform to SDF-P guidelines (see the “SDF-P” manual[9]).If S procedures or SV jobs are used, the "Rules for S procedures" (see page 79) or “Rulesfor server jobs“ (see page 81) should be noted, respectively.

The SIGNAL and TRANSFER programs can be integrated into jobs or S procedures toenable runtime logs to be transferred to a central library administered by AVAS. The logsare made known to AVAS by the SIGNAL program and transferred to the central library bythe TRANSFER program.Logs of SV jobs cannot be collected via SIGNAL and TRANSFER.

The jobs, S procedures and SV jobs are stored in the job library JCLLIB. They can be madeaccessible to all users by copying them to the system job library JCLSYS (see the COPY-SYSTEM-ELEMENT statement).

Once created, the jobs, S procedures and SV jobs are combined to form a job net, knownfor short as a net. The properties of the net must be set down in the net structuredescription. As well as the jobs, this also contains dependencies as structure elements. Anet structure is created using the CREATE-NET-DESCRIPTION statement. It is stored inthe net library NETLIB. Once stored, a net structure can only be modified by means of the

50 U5184-J-Z125-7-76

User masks

MODIFY-NET-DESCRIPTION statement. The net description can be made accessible to allusers by copying it to the system net library NETSYS (see the COPY-SYSTEM-ELEMENTstatement).

Documentation elements can be assigned via the net description:

– to the net as a whole

– to the individual structure elements of the net.

The documentation elements are stored in the documentation library DOCLIB. Thedocumentation elements can be made accessible to all users by copying them to thesystem documentation library DOCSYS (see the COPY-SYSTEM-ELEMENT statement).

3.1 Creating the AVAS user masks

User masks can be used to supply jobs with current runtime parameters. To do this, the jobsmust be given dummy parameters, which are replaced by values from the user masks. Inthis way, the variables in a job can be modified at the production preparation stage with thecurrent values required for each run, i.e. they can be replaced and assigned to the job.

User masks can be created using FHS or IFG. AVAS supports +-formats and #-formats inthe user masks; #-formats should preferably be used, to enable the interface to be trans-ferred to FHS-DOORS (see the “FHS” manual [5] or the “IFG” manual [6]).

There are two kinds of user mask:

– masks for entering parameters which are valid throughout the net, i.e. net parameters(COLLECT-NET-PARAMS statement) and

– masks for entering parameters for a particular job (CREATE-PROD-NET/JOB state-ments), which are called from the job via an AVAS statement (#AVM#).

As regards the information, control and message sections, every user mask must have thesame structure as a system mask.

Lines 2 through 21 contain the application-specific processing section.

The control section must contain the variable fields for the operation, statement andoperands, with the text field names and the sequence of entries being the same as in thesystem masks. Interchanging these mask fields will cause processing errors.

The same remarks apply to the message section as to the control section.

If a user mask does not comply with the prescribed AVAS conventions, it is not possible toperform parameter modification via masks. The mask is rejected by AVAS with an errormessage.

U5184-J-Z125-7-76 51

User masks

The user is responsible for assigning the variable fields in the masks to the variables in thejobs and JCL elements. When creating masks, he should make sure that these variablesare not used more than once per mask, and remember that only the most recently enteredvalues apply during subsequent processing (no memory function). This means that a maskmust contain all the information required for the subsequent processing operation.Values are assigned using the FHS parameters EXIT and REM; the name of the AVASvariable must be specified under REM.

When IFG is used, EXIT=YES and REM=name must be specified for the variable fields,where "name" is the name of the AVAS variable.

Storing user masks in libraries

The masks used for collecting net parameters (net masks) and for entering job parametersvia a mask called in the job (job masks) can be stored in different mask libraries. AVASexpects net masks to be in the NETMAP library, and job masks in the JOBMAP library.When masks are created using FHS or IFG, the names of the libraries must be specified(see the “FHS” manual [5] or the “IFG” manual [6]).

There are no special AVAS rules for assigning mask names. However, the names must notbegin with AVM$... as this character string is reserved for AVAS system masks. The usershould set up rules for assigning mask names that allow him first of all to tell whether a usermask is a net mask or a job mask, and then to assign a user mask to a particular net orgroup of nets. Since net masks require different system fields than job masks, interchangingthe masks will lead to processing errors in the assigned AVAS components.

The names must be unique throughout all the mask libraries. This is because the masksare kept resident once they have been loaded for the first time from the FHS mask library,and when the mask name is called again the library entry is no longer processed (the maskis first sought in the internal FHS mask table, where in this case it is also located anddisplayed).

52 U5184-J-Z125-7-76

User masks

User masks for net modification

When setting up a user mask for collecting net parameters (COLLECT-NET-PARAMSstatement), note the following rules:

Each user mask must always be formatted in the same way as a system mask (seepage 14).

The system parameters S#003 (net name) and S#004 (net status), can be specified in theprocessing section. These parameters are then assigned the appropriate current valueswhen the mask is displayed. Entries in the S#nnn fields are not processed.The location of the user parameters within the processing section is freely selectable. Theuser parameters, AVAS variables N#001 to N#999, are valid for one net and must notappear more than once in the same mask.

Several net masks may be used for one net definition. When two or more masks are definedfor collecting net parameters, the user parameters must be unique throughout all the masks.AVAS does not check that this is the case; each user is responsible for the values assignedto the parameters.

Entry of the parameters for netwide modification (COLLECT-NET-PARAMS) must beperformed before the production preparation stage (CREATE-PROD-NET). If the sameuser parameter is included in more than one mask, it is affected the corresponding numberof times (for each mask) whenever the user parameters are entered or modified.

In the course of production preparation, the user parameters which are valid throughout thenet (AVAS variables N#nnn) are replaced by the value from the first user mask defined andedited in the net.

User masks for job modification

As a rule, user masks for job modification (CREATE-PROD-NET/CREATE-PROD-JOBstatements) are formatted in the same way as system masks (see page 14).

The processing section may contain the system parameters S#003 (net name), S#004 (netstatus), S#005 (job name) and S#006 (job status), which are then supplied with the appro-priate current values when the mask is displayed. Entries in the S#nnn fields are notprocessed.The AVAS variables P#001 through P#999 should be employed as user parameters.The values of these variables in a user mask are retained only until another user mask iscalled or until the processing initiated via CMD:EXECUTE is terminated.

The same user parameter must not occur more than once in a mask. This rule holds trueeven when two or more job modification masks are defined, since each time a value isentered via another mask a new value is assigned to the user parameter.

U5184-J-Z125-7-76 53

User masks

Example of user mask format

The following sample mask, created with FHS, illustrates net modification.

For information on FHS macros see the “FHS” manual [5].

AVAS-Vnn.yxmm/format format-description ########/########

user-param-description

NET-NAME= ____________________________ NET-STATUS=____________________

VOLUME : ________________

DATEINAME : __________________________

CMD: _____________________ OPR: ______________________________________________________________________________________________________________________________________MSG: _____________________________________________________________________________

54 U5184-J-Z125-7-76

User masks

Meanings of the mask fields

Line 1: Information section

AVAS-Vnn.yxmm/ AVAS system version (optional)

nn = main version of the AVAS systemy = revision versionxmm = version update

FHS macro calls:nn MDFLD POS=(1,1),LEN=13,EXIT=YES,REM='SYSVERS'

format Name of the mask (optional).Up to 8 characters are allowed.

FHS macro call:MDFLD POS=(1,15),LEN=8,ATTR=(PROTRET)

format-description Designation of the mask (optional).The length is limited only by the number of columns available(e.g. the maximum length for POS=(1,22) is 40).

FHS macro call:MDFLD POS=(1,22),LEN=40,ATTR=(PROTRET)

########/######## Date/Time of day in the form:dd.mm.yy/hh:mm:ss

FHS macro calls:Date MDFLD POS=(1,63),LEN=8,ATTR=(PROTRET),

EXIT=YES,REM=C'S#001'MDFLD POS=+0,CONT='/'

Time MDFLD POS=(1,72),LEN=8,ATTR=(PROTRET),EXIT=YES,REM=C'S#002'

U5184-J-Z125-7-76 55

User masks

Lines 2 through 21: Processing section

user-param-descriptionPurpose of the mask (optional).The length is limited only by the number of columns available.

NET-NAME=netnameName of the net.The variable field must be defined.Specification of the text field is optional. In this example it has thename NET-NAME=.

FHS macro calls:MDFLD POS=(7,2),CONT='NET-NAME='

netname MDFLD POS=(7,11),LEN=32,ATTR=(PROTRET), EXIT=YES,REM=C'S#003'

NET-STATUS=keywordStatus of the net.The variable field must be defined.Specification of the text field is optional. In this example it has thename NET-STATUS=.

FHS macro calls:MDFLD POS=(7,48),CONT='NET-STATUS='

keyword MDFLD POS=(7,60),LEN=20,ATTR=(PROTRET), EXIT=YES,REM=C'S#004'

VOLUME Data volume.

FHS macro calls:MDFLD POS=(11,4),CONT='VOLUME : '

volume MDFLD POS=(11,16),LEN=8,ATTR=(UNPROT), EXIT=YES,REM=C'N#nnn'

FILE-NAME Name of the file.

FHS macro calls:MDFLD POS=(13,4),CONT='FILE-NAME : '

file-name MDFLD POS=(13,16),LEN=24,ATTR=(UNPROT), EXIT=YES,REM=C'#nnn'

56 U5184-J-Z125-7-76

User masks

Lines 22 and 23: Control section

CMD:______________________

Input field for the statement name and the operations.Length = 22 characters

OPR:_____________ ...

_______________________ ...

Input field for the operands. Length = 129 characters. The operandsmust be specified in the form name1=value1[,name2=value2]... .

FHS macro calls for the control section:MDFLD POS=(22,1),LEN=4,CONT='CMD:'

SYSCMD MDFLD POS=(22,5),LEN=22,ATTR=(UNPROT,BRT[,IC]),EXIT=YES,REM=C'SYSCMD'

MDFLD POS=(22,27),LEN=5,CONT=' OPR:'SYSOPR MDFLD POS=(22,32),LEN=129,ATTR=(UNPROT,BRT),

EXIT=YES,REM=C'SYSOPR'

Line 24: Message section

MSG:___________________ ...

Area for execution, system and error messages.Length = 75 characters.

FHS macro calls for the message section:MDFLD POS=(24,1),LEN=4,CONT='MSG:'

SYSMSG MDFLD POS=(24,5),LEN=75,ATTR=(PROT,BRT),EXIT=YES,REM=C'SYSMSG'

U5184-J-Z125-7-76 57

User masks

Creating the AVAS user masks with IFG (see also the “IFG” manual [6])

An AVAS user mask for modifying global net parameters has been selected as an example.

Key: _ Input data field$ Output data field

Both the steps that only have to be performed once when creating a IFG user profile as wellas the calls that occur repeatedly to create the mask are shown in each IFG mask.Only the modifications necessary for AVAS masks are described in each mask. Other IFGdescription options in respect of the AVAS user masks can be selected if required.

Once IFG has been loaded, the following functions for defining the format file and userprofile are required, assuming this has not already been done.

IFG mask: INTERACTIVE FORMAT GENERATOR 0001 Enter: Name of format library: ........ Select: User profile administration

IFG mask: USER PROFILE ADMINISTRATION 0701 Select: Do you want to set up the IFG standard profile?

IFG mask: USER PROFILE ADMINISTRATION 0701 Select: Do you want to modify part of the user profile?

IFG mask: MODIFYING YOUR USER PROFILE 0702 Select: Default values for the use of IFG

______________/NETPARAM format-description $$$$$$$$/$$$$$$$$

user-param-description

NET-NAME=$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ NET-STATUS=$$$$$$$$$$$$$$$$$$$$

VOLUME : ________________

DATEINAME : __________________________

CMD: _____________________ OPR: ____________________________________________________________________________________________________________________________________MSG: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

58 U5184-J-Z125-7-76

User masks

IFG mask: MODIFYING YOUR USER PROFILE 0703 DEFAULT VALUES FOR THE USE OF IFG Modify: Retain field attributes: YES Modify: Max. number of used lines/columns in formats ... : 24 /080

Note: Changing the maximum number of used lines to 24 is not mandatory for AVAS; it does, however, correspond to the layout of the AVAS system masks and to the default of the sample mask being used.

IFG mask: MODIFYING YOUR USER PROFILE 0702 Select: Input/validation attributes for each field type

IFG mask: MODIFYING YOUR USER PROFILE 0708 INPUT/VALIDATION ATTRIBUTES FOR EACH FIELD TYPE Text Input Input field Output field field numeric field Modify: Automatic input: NO YES YES YES

IFG mask: MODIFYING YOUR USER PROFILE 0702 Select: Application library specifications

IFG mask: MODIFYING YOUR USER PROFILE 070B DEFAULT VALUES FOR FORMAT PREPARATION FOR FHS APPLICATION LIBRARY SPECIFICATIONS Enter: Preparation of In library - Formats : YES NETMAP | JOBMAP - Addressing aids: YES ...............

Note: regarding NETMAP | JOBMAP The DMS names for the NETMAP or JOBMAP are contained in the "Generation" chapter of "AVAS for the Administrator" [3]. The file name listed for NETMAP or JOBMAP is to be entered here. regarding addressing aids If the input/output is processed using the AVAS computer center exits for the user masks, a library name is to be specified and YES entered in response to the format preparation query.

U5184-J-Z125-7-76 59

User masks

Once the user profile has been modified, the calls to create a mask are issued as follows:

IFG mask: INTERACTIVE FORMAT GENERATOR 0001 Select: Create format

IFG mask: CREATING A FORMAT 0101 Enter: Format name ........: NETPARAM

Note: regarding NETPARAM The format name NETPARAM has been chosen at random for the purposes of this example. The name of the user mask is to be entered here. The mask name must not start with the characters AVM$.

IFG mask: DRAFTING AN IMAGE FOR FORMAT <format> 0110 Enter: Layout of the sample mask, or image desired for <format>. Useful information on this topic can be found in the manual "IFG for FHS.

Note: The layout of the entire mask is defined in this IFG mask.

Once the layout of the sample mask or another AVAS user mask has been defined, eachfield in the mask is described in more detail in the subsequent IFG masks. Only global datais specified for the IFG masks. The values for each field of the sample mask are defined inthe table that follows.

IFG mask: CREATING THE FORMAT <format> 0104 Select: - the display attributes of the format fields Select: - the symbolic names of the format fields Select: - the input/validation attributes of the format fields (part I) Select: - the editing attributes of the format fields

Note: In this IFG mask, the lines shown above must be selected one after the other. In the following IFG masks, the user determines the attributes and names for the individual mask fields.

IFG mask: DISPLAY ATTRIBUTES OF FORMAT <format> 0305 Enter: YES or NO to select display attributes for the highlighted field.

IFG mask: FIELD NAMES OF FORMAT <format> 0306 Enter: No entries for AVAS user masks need to be made in this IFG mask. If, however, the mask is to be edited by the user via the AVAS computer center exit AVEX6601 and/or AVEX6602 (or AVEX6801 and/or AVEX6802), field names for an addressing aid can be specified here.

60 U5184-J-Z125-7-76

User masks

IFG mask: INPUT/VALIDATION ATTRIBUTES (1) OF FORMAT <format> 0307 Enter: No entries for AVAS user masks need to be made in this IFG mask.

IFG mask: EDITING ATTRIBUTES OF FORMAT <format> 0308 Enter: The corresponding identifier for each field to be taken into account when using AVAS to modify a net (or job in the case of job masks) is to be specified (identifier = computer center exit code (REMARK):). The identifiers N#001 and S#001, among others, are used in the sample mask. The other editing attributes are to be defined as shown in the following table.

The mask description is now complete. To enable the mask description data to be accessedfrom AVAS, format preparation under the names that AVAS uses is required.The following IFG masks must be called for this purpose:

IFG mask: INTERACTIVE FORMAT GENERATOR 0001 Select: Prepare format

IFG mask: FORMAT PREPARATION 0501 Enter: - Do you want your format application file to be updated? YES Enter: - Do you want your addressing aids library to be updated ? YES or NO

Note: You must reply YES to the prompt regarding the addressing aids library if you are working with the AVAS computer center exits described above.

U5184-J-Z125-7-76 61

User masks

Table of fields and field attributes in the sample mask

(1) Line (0110) - The number in brackets is the number of the IFG mask

(2) Column (0110)

(3) Length (0110)

(4) High-intensity: (0305)

(5) Low-intensity: (0305)

(6) Field accessible by program (0306)

(7) Protected (0307)

(8) Input/output left-justified (0308)

(9) Uppercase only (0308)

(10) Processing by exit (0308)

(11) Exit code (REMARK) (0308)

*) The field attributes below have been changed.

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) Comments

1 1 13 NO *)

YES YES NO YES NO NO In AVAS masks the version, inuser masks anything, so thathard copy can be initiated

1 14 1 NO YES NO YES NO NO NO Separator between version andmask name

1 15 8 NO YES NO YES NO NO NO Mask name(e. g. NETPARAM)

1 31 18 NO YES NO YES NO NO NO Title or mask heading

1 63 8 NO YES YES YES NO NO YES *)

S#001 *)

System variable date of modifi-cation

1 71 1 NO YES NO YES NO NO NO Separator between date andtimet

1 72 8 NO YES YES YES NO NO YES *)

S#002 *)

System variable time of modifi-cation

5 2 22 NO YES NO YES NO NO NO Section heading within a mask

7 2 9 NO YES NO YES NO NO NO Name for the next input field

7 11 32 YES *)

NO YES YES NO NO YES *)

S#003 *)

System variable net name forthe modification


7 60 20 YES *)


S#004 *)

System variable Net status forthe modification


11 16 6 YES NO YES NO YES YES *)

YES *)

N#001 *)

Net variable Tape number of themodification

62 U5184-J-Z125-7-76

User masks

Restrictions

With IFG, the operand area cannot be defined as a field.

Notes

– Lines 22 to 24 must be defined as shown in the example. The cursor can be positionedanywhere.

– Processing by (computer center) exit and the exit code must be entered as shown in theexample.

– Output fields in the mask that are filled via system parameters (S#nnn) must be definedas output fields with automatic input.

– If the user enters an end marker in the mask (EM key), the message AVS4070 may beoutput.



YES *)

N#002 *)

Net variable File name for themodification

22 1 4 NO YES NO YES NO NO NO Name for the AVAS statementfield


YES *)

SYSCMD *)

AVAS system field for statement

22 27 5 NO YES NO YES NO NO NO Name for AVAS operand field 1stpart


YES *)

SYSOPR1 *)

AVAS system field for theoperand’s 1st part


YES *)

SYSOPR2 *)

AVAS system field for theoperand’s 2nd part

24 1 4 NO YES NO YES NO NO NO Name for the AVAS messagefield

24 5 75 YES *)


SYSMSG *)

AVAS system field for themessages

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) Comments

U5184-J-Z125-7-76 63

SHOW-FORMAT

SHOW-FORMATDisplay user mask

The SHOW-FORMAT statement enables each user to display the user masks stored in amask library (NETMAP or JOBMAP). The libraries must be of the type PLAM. Thisstatement cannot be used to display AVAS system masks.

FORMAT-NAME=Name of the user mask to be displayed.

FORMAT-NAME=formatThe name of the user mask can be up to 8 characters long, but it must not begin with"AVM$".A partially qualified name causes the overview of user masks to be displayed. If the operandis not specified, AVAS assumes FORMAT-NAME=*.

AVAS-USER-LIBRARY=Name of the mask library from which the user mask is to be read.If the operand is not specified, the default value NETMAP applies.

AVAS-USER-LIBRARY=NETMAPThe net mask is read from the library of user masks for net modification.

AVAS-USER-LIBRARY=JOBMAPThe job mask is read from the library of user masks for job modification.

Notes

– The S#nnn fields defined in the user mask are already supplied with values whendisplayed.

– If the user mask was displayed previously during the current AVAS session (by meansof COL-NET-PARAM, CREA-PROD-NET/JOB or a preceding SHOW-FORMAT),modifications subsequently made to the mask can be redisplayed only after the TIAMtask has been terminated and restarted (the masks are kept resident).For this reason, it is not advisable to have user masks with the same name but withdifferent structures (different versions) stored in the mask libraries NETMAP andJOBMAP.

SHOW-FORMAT

[,FORMAT-NAME=format]

[,AVAS-USER-LIBRARY=NETMAP | JOBMAP ]

64 U5184-J-Z125-7-76

Mask AVI015 SHOW-FORMAT

AVI015 - Overview of user masks

DATE Output parameter.Date of last modification.yyyy-mm-dd

FORMAT-NAME Output parameter.Name of the user mask.

M Input parameter.

S (Select) The mask is selected for display.

U5184-J-Z125-7-76 65

AVAS statements and variables

3.2 AVAS statements and variables in jobs, S procedures, serverjobs and JCL elements

Jobs, S procedures, SV jobs and JCL elements are created and edited in the user libraryJCLLIB by means of the EDIT-JOB statement.

When jobs, S procedures, SV jobs and JCL elements are created or edited, it is possible toincorporate additional information into the JCL statements. This is done by predefiningsymbolic names, which are interpreted by the AVAS system as AVAS statements and AVASvariables. They can only be used in the following contexts:

– facilities for adapting values which vary from run to run

– facilities for assigning JCL elements which are stored externally

– facilities for passing run control information to AVAS with the aid of a task job variable

– restart facilities following errored behavior on the part of a task.

AVAS statements are executed within the framework of modification. The run control infor-mation is evaluated by the run control system.

The following symbolic names, when used in jobs, S procedures, SV jobs and JCLelements, are automatically reserved by the AVAS system and are interpreted asstatements. They must be located in the task starting at column 1 of a record.

AVAS statements can also be entered as /REMARK or /WRITE-TEXT commands. In thiscase, they must begin in column 9 or column 15, respectively:

/REMARK #AVM#..../WRITE-TEXT C’#AVM#....

Symbolic name Function of the statement

#AVM# Assign a mask for run parameter input.

#AVS# Call a JCL element.

#AVD# Call an element from any library or file

#AVJ# Send information to AVAS using a task job variable.

#AVA# Enter information in the journal

#RA In the event of a restart, replace the next statement by the contents of thisstatement.

#RI In the event of a restart, insert the contents of this statement.

#RU In the event of a restart, suppress the next statement.

66 U5184-J-Z125-7-76

AVAS statements and variables

Jobs containing AVAS statements in /REMARK or /WRITE-TEXT commands can beexecuted under BS2000 without being modified. The function of the AVAS statements,however, is only carried out at the production preparation stage within AVAS (CREATE-PROD-NET/JOB). AVAS recognizes the symbolic names of the statements, even ifpreceded by /REMARK or /WRITE-TEXT commands, and performs the correspondingfunction.

The following symbolic names are recognized as AVAS variables. They may be located inany record, starting at any location within that record.

The symbolic name indicators P#, S#, N# and F#, which are normally preset for the AVASsystem, can be defined differently by the AVAS administrator. Internal processing ishowever optimized on the use of the standard indicators. The functions of the statement andvariable codes preset on the system side are described in the following sections, togetherwith the character strings thereby reserved.

Symbolic name Function of the variables

P#nnn AVAS variables from job masks (CREATE-PROD-JOB/NET).

S#nnn AVAS variables from system fields (nnn = 000 - 200)The user’s AVAS variables (nnn = 201 - 999)(CREATE-PROD-JOB/NET).

N#nnn AVAS variables from net masks (COLLECT-NET-PARAMS,CREATE-PROD-NET).

F#nnn AVAS variables from the USER-PARAM-FILE (CREATE-PROD-JOB/NET).

U5184-J-Z125-7-76 67

AVAS statements

3.2.1 AVAS statements

#AVM# - Assign user mask for run parameter input

If the JCL statements of a task (job, SV job or S procedure) are to be modified with the aidof a user mask, the #AVM# statement must be specified in the task. This statement assignsthe corresponding user mask to the task. The #AVM# statements are processed within theframework of job modification (see the CREATE-PROD-JOB/CREATE-PROD-NET state-ments), and in each case cause the associated user mask to be displayed. In the course ofthis operation, the AVAS variables (P#nnn) are assigned the current values of the runparameters. These values remain valid until the next user mask of the task appears or untilthe processing initiated via CMD:EXECUTE is terminated. Only those AVAS variablesbelonging to the most recent user mask take effect.

#AVM# Symbolic name of the statement. It must begin in column 1 or belocated after /REMARK or /WRITE-TEXT.

format Name of the user mask assigned when the mask was created withFHS/IFG (see page 50). The name may be up to 8 characters longand must immediately follow the AVAS statement.

text Any text (comments) entered must be located in columns 21-70.

The #AVM# statement must not be used in a JCL element.In S procedures and SV jobs, the #AVM# statement is only evaluated in the parameter area.

#AVM#format [text]

68 U5184-J-Z125-7-76

AVAS statements

#AVS# - Call JCL element

This statement calls a JCL element stored in the JCLLIB or JCLSYS library, and incorpo-rates it in the element during job modification at the location where the #AVS# statementwas issued.The JCL element may be an element with BS2000 commands, server statements or datarecords.

A JCL element may contain AVAS variables, AVAS restart statements and #AVJ# state-ments for defining the task job variable, but it must not contain any #AVM#, #AVS# or#AVD# statements.

JCL elements can be used in jobs (BS2000), S procedures and SV jobs. The JCL elementsin the JCLLIB and JCLSYS are assigned the relevant function J, P or X.During modification, the specified function of the element used is checked for validity.

The following combinations are permitted:

#AVS# Symbolic name of the statement. It must begin in column 1 or belocated after /REMARK or /WRITE-TEXT.

$ug_name Name of a JCL element from the JCLLIB or JCLSYS.

If a user group $ug_ is specified, it must be either the user group ofthe net in which the element is used or the system user groupBKSYS ("BK" being the German abbreviation for user group).If no user group is specified, the JCL element is first sought in theJCLLIB and then, if not found there, in the JCLSYS.The name of the element must come directly after the symbolicname #AVS# (it must not contain blanks). The name (without $ug_)can be up to 24 characters long.

text If any text (comment) is entered, at least one blank must bespecified between the name of the element and the text.

Nesting of #AVS# statements is prohibited.

Element Function of the element

Job (FU=J) FUNCTION=J

S procedure (FU=P) FUNCTION=P or J

SV job (FU=X) FUNCTION=X

A JCL element with a different function will not be found by the CREATE-PROD-JOB/NETstatements.

#AVS#[$ug_ ]name [text]

U5184-J-Z125-7-76 69

AVAS statements

In S procedures and SV jobs, the #AVS# statement is evaluated only in the procedure areaor job area.

If parameters are specified after the separator string in a JCL element with the functionFU=P/ X, these are not transferred to the JMDLIB.

The elements used in an S procedure or SV job are not modified.

#AVD# Call external element

This statement calls an element stored in any library or file and places it at the location atwhich the #AVD# statement is issued during job modification.

The element that is read in is not subject to modification and is entered unchanged in theelement.

The element must not contain any AVAS variables or #AVM#, #AVS# and #AVD# state-ments.The element is logged in the journal (CREATE-PROD-NET).The elements can be used in jobs (BS2000), S procedures and server jobs.The #AVD# statement is only evaluated in S procedures and server jobs in the JCL area,but not in the parameter area.

#AVD# Symbolic name of the statement. It must begin in column 1 or belocated after /REMARK or /WRITE-TEXT.

filename Name of the file in which the element is stored.The name can be up to 54 characters long.

lib(element[,type]) The element is sought in the specified element of the defined librarywith the specified type of library department.If the type of library department is not specified, type S is used.The expression can be up to 72 characters long.

text If any text (comment) is specified, at least one blank must beentered between filename or lib(element[,type]) and text.

Note

A file or a library element must come directly after the symbolic name #AVD# (it mustnot contain blanks).

#AVD#filename|lib(element[,type]) [text]

70 U5184-J-Z125-7-76

AVAS statements

#AVJ# - Set errors and restart variant via task job variables

This statement makes it possible to set errors and, optionally, to enter additional messagesin the journal file. When outputting JCL statements from the run control file to the ENTERfile, the AVAS run control system converts this statement to the BS2000 command

/MODIFY-JV JV=(JV-NAME=jvname,POSITION=129,LENGTH=55),SET-/VALUE=C’RV=n,text’

The name of the task job variable ("jvname") is assigned by the run control system.

#AVJ# Symbolic name of the statement. It must begin in column 1 or belocated after /REMARK or /WRITE-TEXT.

RV=n This specifies the restart variant with n = 0, 1, 2 or 3.

If n is equal to 1, 2 or 3, the error text is to be stored in the journalfile and the prompt INITIATE RESTART VARIANT n is to be output tothe associated console.

If AUTOMATIC=YES has been specified in the restart variantselected via RV=n, the run control system automatically initiatesrestart via the specified variant.If AUTOMATIC=YES has not been specified, no automatic restart isinitiated (the other variants are not searched for AUTOMATIC).

If n=0 the error text is stored in the journal file. No output to theconsole occurs. Then, for RV=0, the restart variants 1, 2 and 3 aresearched for AUTOMATIC.

If no automatic restart can be initiated (AUTOMATIC=NO) and arestart variant has been set via RV=n, the restart requested by theRESTART-NET statement is initiated through the defined variantunless the user enters a different restart variant using the parameterfields of the assigned masks.

errortext Any text, up to 55 characters long.It is stored in the journal file regardless of the value n.

If RV=n is not specified, only the text is entered in the task jobvariable and is displayed via SHOW-NET-STATUS. The contents ofthe job variable are output to the journal file with the record key52-07 or 52-08.

#AVJ#RV=n,errortext

U5184-J-Z125-7-76 71

AVAS statements

Note

In BS2000 the monitoring job variable can be accessed via its file link name. Therefore,instead of the AVAS statement #AVJ# itself, the user can issue the BS2000 commandresulting from it by using its file link name to reference the task job variable allocated bythe run control system:

/MODIFY-JV JV=*LINK(LINK-NAME=*SMONJVJ,POSITION=129,LENGTH=55),-/ SET-VALUE=C’RV=n,text’

Note that no additional blanks may be specified in the string ’LINK-NAME=*SMONJVJ’.LINK-NAME=*SMONJVJ must be specified in the same statement line.

The run control system evaluates the monitoring job variable in conjunction with the valuesentered via BS2000 and the #AVJ# statement, and sets the following statuses for the job inquestion:

– In server systems, the monitoring job variable is simulated via a JV file. The informationis transferred from the server host to the BS2000 host by an AVAS utility routine, andfrom there is entered in the task job variable.When the JCL statements of a script from the server systems are output, the AVAS runcontrol system converts the #AVJ#text statement into avssinjv ´text´

The AVAS utility routine AVSSINJV places the specified text in the JV file. AVSSINJVmust be known in the server system.

With SV jobs, the run control system evaluates the task job variable in conjunction withthe values entered by the AVAS agent in the server system and the #AVJ# statementor the AVSSINJV program, and sets the following conditions for the job:

Contents of the task job variable Job statusfor AVAS

Restartpossible?BS2000 status

valuesValue created by the#AVJ# statement

$A$A$T$T

no value (129,3)and value (129,3),C' RV='and value (129,3),C' RV='no value (129,3)

end with errorend with errorend with errornormal end

yesyesyesno

Contents of the task job variables Job statusfor AVAS

Restartpossible1st byte of server

status (byte 184)Value created by the#AVJ# statement

AATT

no value (129,3)and value (129,3),C' RV='and value (129,3),C' RV='no value (129,3)

end with errorend with errorend with errornormal end

yesyesyesno

72 U5184-J-Z125-7-76

AVAS statements

The BS2000 status value of the AVAS agent AVSSINCM has no relevance for deter-mining the job status of SV jobs.

#AVA# Enter information in journal

This statement enters information in the journal file. When outputting the JCL statementsfrom the run control file to the ENTER file, the AVAS run control system converts thisstatement into the following two BS2000 commands:

/WAIT-EVENT UNTIL=*JV(COND=((jvname,1,1)=C' '),TIME-LIMIT=600)

/MODIFY-JV JV=(JV-NAME=jvname,POSITION=1,LENGTH=256),SET-VALUE=text

The name of the communication job variables (jvname) is set by the run control system. The/WAIT-EVENT command is used to prevent a text that has not yet been collected by the runcontrol system from being overwritten.

#AVA# Symbolic name of the statement. It must begin in column 1 or belocated after /REMARK or /WRITE-TEXT.

text Text, which is to be entered in the journal file using the record key08-01.The text must begin with the character $.

$J,... makes an entry in the journal file$M,... makes an entry in the journal file and the information MODIFIED is

also stored for the net.

If the text does not begin with the character $, AVAS assumes thata text containing $x,... appears for the journal file in another user jobvariable.In this case, the JV-NAME or LINK-NAME syntax of the SET-VALUE= parameter of the BS2000 command /MODIFY-JV must beadhered to for text.

Notes

– The AVAS statement #AVA# is only processed for structure elements with TYPE=STDor TYPE=MOD and FU=J or FU=P.

– The AVAS statement #AVA# does not bring about the ERROR status of the structureelement in question. This can be achieved using the AVAS statement #AVJ# or with theabnormal termination of the job run.

#AVA#text

U5184-J-Z125-7-76 73

AVAS statements

Statements for restart case #Rx

If, during net processing, errors occur in an associated job, these errors can be recoveredor circumvented in another net processing run. To this end, it must be ensured whendefining the job that the net can be restarted by the RESTART-NET statement, i.e. that thejob is given the status ERROR by AVAS. This can be done using, for example, the BS2000command /ABEND or the AVAS statement #AVJ#.

Furthermore precautionary measures in the jobs can be taken, in the form of restart state-ments. The restart statements define whether and if so how the individual JCL statementsshould process the jobs and JCL elements in the event of an error. For example, JCL state-ments can be interchanged (#RA), suppressed (#RU) or executed in addition (#RI).

Only when the net is processed in RESTART mode will the functions in the restart state-ments be executed by the run control system.

The table below shows when the restart statements are processed:

Restart statement Meaning

#RA The JCL statement following the #RA statement in the job is to bereplaced by the JCL statement defined with #RA. This is done byshifting the contents from position 4 (without #RA) to positions 1-71of the following JCL statement. The contents of column 72 andonwards are retained.If necessary, the continuation character must be entered in column75 of the JCL statement defined with #RA.The statement following the #RA statement must not be an AVASstatement as otherwise this will likewise be replaced by the #RAstatement.

#RI The contents of this statement are to be inserted in the job as a JCLstatement. To do this, the contents are shifted from position 4(without #RI) to position 1.If necessary, the continuation character must be entered in column75 of the JCL statement defined with #RI.

Symbolic name of therestart statement

RESTART-TYPE=

NORMAL RESTART

#RA no yes

#RI no yes

#RU no yes

74 U5184-J-Z125-7-76

AVAS statements

#RU The next statement is to be suppressed.The statement following the #RU statement must not be an AVASstatement as otherwise this will likewise be suppressed.

If the restart statements are entered as BS2000 /REMARK commands, the contents areshifted from position 12 to position 1.If the restart statements are entered as BS2000 /WRITE-TEXT commands, the contentsfollowing the first single quote (from position 19) are shifted to position 1.The concluding single quote is deleted.

The processing of restart statements within the nets is canceled when the run controlsystem for the net in question switches to normal processing mode (N mode).In the restart job index level range from 900 to 999, the switch from RESTART mode toNORMAL mode can be controlled via the parameter RESTART-TYPE of restart variant 1.RESTART mode is exited by specifying RESTART-TYPE=NORMAL for restart variant 1.RESTART mode is automatically left when the first index level of normal processing (index001 through 899) has been completely processed.

For a general description of the restart procedure, see section “Preparing for the restart” onpage 120.

U5184-J-Z125-7-76 75

AVAS variables

3.2.2 AVAS variables

Values (run parameters) which are to be different from run to run can be specified in jobsand JCL elements as AVAS variables. The symbolic name of the AVAS variable mustalways be preceded by the number nnn, which must consist of three digits.These variables are converted into current values at the production preparation stage withinthe framework of job modification.The AVAS statement #AVM# in a job causes a user mask to be displayed. When this isdone, the variable fields in the user mask are assigned AVAS variables, e.g. P#nnn. In thisway, the AVAS variables used in jobs and JCL elements can be addressed and modifiedwith the aid of the user masks.Modification causes an executable copy (production job) ofthe job from the JCLLIB or JCLSYS library to be created in the JMDLIB library. The AVASvariables are replaced by current values in the (output) records of the production job thuscreated.

If a record comprises only AVAS variables and no values are assigned to these, the emptyrecord thereby generated will not be output.

AVAS variables S#

These AVAS variables can be used in all jobs and JCL elements which are subject to modifi-cations (CREATE-PROD-NET/-JOB).

Depending on the numeric part of the name key S#nnn, a differentiation is made between– variables from the system fields (reserved value range 000 - 200) and– user variables (nnn = 201 - 999).

An S#nnn field can be addressed as often as you want.

AVAS system field variables S#

The fields with the keys S#001 and S#002 are taken from the most recently displayed maskand added to the output record; the other fields are taken from a data area internal to theAVAS system.

Key Value Length

S#001 dd.mm.yy current date mask field (8)

S#002 hh:mm:ss current time of day mask field (8)

S#013 yymmdd current date 6

S#012 hhmmss current time of day 6

S#003 netname NET-NAME with BK_, _date_time 32

S#011 netname NET-NAME without BK_, _date_time variable (max:12)

S#004 keyword for NET-STATUS variable

76 U5184-J-Z125-7-76

AVAS variables

(Note: "BK" is the German abbreviation for "user group".)

The values for S#013 and S#012 are redefined for a net which is to be modified, and remainthe same until net modification has finished.If the fields S#001 and/or S#002 are not present in the mask, the variables are set via thecurrent system time.

AVAS user variables S#

The fields containing the keys S#201 to S#999 and the values assigned to them can bedefined by the AVAS administrator at generation time and/or can be modified, deleted andcreated using the MODIFY-SYSTEM-PARAMS statement.

The defined value of the variables is used during modification.The assigned value of the variables is made up of any character string consisting of 1 to 48characters.

If “value“ is specified in quotation marks, the character string can contain blanks. Twoquotation marks must be entered for one quotation mark within “value“.

AVAS job mask variables P#

The AVAS variables P#nnn can be used in all jobs and JCL elements which are subject tothe performance of modifications (see the CREATE-PROD-NET and CREATE-PROD-JOBstatements). A P#nnn field can be addressed as often as you want. The P#nnn variablesare available until a new mask is assigned (system mask or user mask).

The format of the record in the production job (output record) is governed by the followingrules:

– The variable field addressed by the AVAS variable P#nnn is included in the outputrecord in the length with which it was defined when the user mask was generated. Thecontents of the input record are shifted accordingly. (The input record is the record inthe job with the symbolic name of the AVAS variable.)A field therefore always occupies five positions in the input record, and 1-80 positionsin the output record.

Key Value Length

S#005 jobname JOB-NAME (from net descr. [with BK_]) 30

S#014 jobname INPUT-JOB-NAME without BK_ variable

S#015 jobname OUTPUT-JOB-NAME without BK_ variable

S#006 keyword for JOB-STATUS variable

U5184-J-Z125-7-76 77

AVAS variables

Provided the following conditions are met, positions 72-80 are taken unchanged fromthe input record to the output record:

If AVAS variables cause shifts to occur, characters in the input record will be lost(parameter longer than 5 characters) or blanks will be appended (parameter shorterthan 5 characters).

If BS2000 commands of this type contain AVAS variables in positions 73 through 80,the AVAS variable is not changed and is thus not extended in a current output record.

– If a variable field is to be included in the output record, but not in the length defined whenthe user mask was generated, the end-of-field mark X’4A’ must be entered in this field.The end-of-field mark is represented on data display terminals as C’'’.

In this case, the character string to be added to the output record can be 0-79 positionslong, i.e. the entry of the end-of-field mark at the first position of a variable field causesthe field to be excluded from the output record.

– If fields in which nothing is to be entered are not to be transferred to the output record,the filler character ’'’ must be entered in these fields when generating the user mask(FHS parameter JUST=(N,',N,')).

AVAS net mask variables N#

These variables can only be used in jobs and JCL elements which are subject to net modifi-cation (see the CREATE-PROD-NET and COLLECT-NET-PARAMS statements).An AVAS variable with the symbolic name N# can be used as often as you want, and in anyjobs or JCL elements in the net.

The same rules govern the inclusion of the values of N# variables in the production job asapply to AVAS variables with the symbolic name P# (see above).

AVAS USER file variables F#

These variables can only be used in jobs and JCL elements which are subject to job andnet modification (see the CREATE-PROD-NET and CREATE-PROD-JOB statements). AnAVAS variable with the symbolic name F# can be used as often as you want, and in anyjobs or JCL elements in the net.

The values of F#nnn variables are included in the production job in the length with whichthey are stored in the USER-PARAM-FILE.

– The file must be a SAM file with variable-length records. The maximum record length is124 (including the record length field).

Input record column 01 = ’/’ (BS2000 command)

and column 72 = ’-’ (continuation character).

78 U5184-J-Z125-7-76

AVAS variables

– Each record in the file may only contain one value assignment.

– Format of the value assignments:

F#nnn=’value’Ë*text

nnn three-digit number between 000 and 999.

value any character string consisting of 0 to 72 characters.If ’value’ is specified in single quotes, the string may contain blanks (Ë). If asingle quote occurs within ’value’, the quote must be duplicated. If no singlequotes are specified, the string begins after the equal sign and ends at thefirst blank or at the end of the record.

*text Any text (comments) entered must begin with an asterisk (*). At least oneblank must be specified between value and *text.

– A parameter file can be assigned to a net or a task (FU=J/P/X) via the net description.

– The symbolic name F# must begin at position 1 of the record. It is illegal to intersperseblanks.

Example

Value

F#001='290598' *Day of booking 290598F#030='AV0026' *Volume input AV0026F#040='AV1036' *Volume output AV1036F#050='C''PASSWËËË''' C'PASSWËËË'F#060=ABCËËDEF ABCF#070='C'PASSWËËË'' ¨ Syntax error !

Note

F#nnn values with a syntax error are not used. During modification the messagePARAMETER F#nnn NOT FOUND is output to the journal file.

– During modification of an S procedure and an SV job (FU=P/X), the name of anyparameter in the USER-PARAM-FILE can be selected. This name can be up to 48characters long.

– During modification of a job (FU=J), only parameters with the defined name F#nnn canbe processed.

U5184-J-Z125-7-76 79

AVAS variables

Rules for S procedures

S procedures can be used with TYPE=STD/MOD/EXT/EXX.S procedures with TYPE=EXT/EXX are not managed by AVAS.

Only in the case of S procedures which are defined with the function FU=P and TYPE=MODin the net specification are procedure parameters supplied by the run control system withthe ENTER-PROCEDURE call. These procedure parameters are stored in the JCLLIB/JCLSYS or the JMDLIB/JMDSYS in the element which follows the procedure. AVAS insertsa separator string between the fields, as a separator. This separator string can be definedby the AVAS administrator at generation time. If no parameters are being used, theseparator string is the last record in the element.The separator string must be specified by the user if S procedures are to be imported intothe AVAS system by a COPY-ELEMENT after being created outside the AVAS system.

The two areas (S procedure and procedure parameters) can be edited using the statementsEDIT/SHOW-JOB, EDIT/SHOW-PROD-JOB and MODIFY-SUBMIT-JOB. In EDT, thedisplay uses workfiles 0 and 1.

The parameters are specified by ‘parametername=’When doing so, note the following:

– The parameter name must always start in column 1, may contain 1 - 48 characters, andthis string must not contain any blank characters. It cannot start with “SYS“ and mustend with “=”.

– AVAS variables identified by the key fields P#nnn, N#nnn and F#nnn can be used in theprocedure parameter area as the parameter name.

– AVAS variables identified by the key field S#nnn can be used in the procedureparameter area as the parameter name or as a variable for assigning a value to thespecified parameter name (example: S#nnn= or parametername=S#nnn).

– Statements which have a blank or * in column 1 are not processed during the modifi-cation routine (comments).

– If an arbitrary text item (comment) is specified, it must start with an *. There must be ablank between parametername= and *text.

In the job or net modification routines (CREATE-PROD-JOB/NET), only the procedureparameter area is processed. The S procedure itself is copied unmodified into the JMDLIB.

80 U5184-J-Z125-7-76

AVAS variables

For statements, the format of value assignment and storage is:

Values can be assigned using

– the USER-PARAM-FILE (net/job)

– a net parameter (an AVAS variable from the net masks)

– a job parameter (an AVAS variable from the job masks)The user mask assignment is effected by the #AVM# statement in AVAS.#AVM# is processed only in the procedure parameter area.

– a system parameter.

In addition, JCL elements (#AVS# and #AVD# statements) can be called in the S procedurearea (not in the parameter area).

Unlike when a job is being modified, during modification of procedure parameters a searchis also made for parameter names which do not satisfy the naming conventions for F#nnn,N#nnn and P#nnn.In the case of mask parameters (net parameters and job parameters), REM must be usedto assign the parameter name to a mask field. For system parameters, the user mustspecify in addition the S#nnn parameter name, or its name as modified during generation.

During the modification routine, the value assignments for the specified parameters aresought in the following areas in the order given:

– area containing the variables from the USER-PARAM-FILE (job)– area containing the variables from the job mask– area containing the variables from the net masks– area containing the variables from the USER-PARAM-FILE (net).

If a variable name is used more than once in the various areas (job mask, net mask andUSER-PARAM-FILE), the value of the first variable found (according to the search process)is used.

Note

Positional parameters are not supported for ENTER-PROCEDURE calls (withprocedure parameters) in the run control system.

JCLLIB JMDLIB

parametername= parametername=assigned value

S#nnn= S#nnn=value of S#nnn

parametername=S#nnn

applies only to AVAS variableswith the key S#nnn

parametername=value of S#nnn

U5184-J-Z125-7-76 81

AVAS variables

Rules for server jobs

Server jobs (SV jobs) can be used with TYPE=STD/MOD/EXT.SV jobs with TYPE=EXT are not managed by AVAS.

In the case of SV jobs which are defined with the function FU=X in the net specification, theserver statements and job parameters are supplied by the run control system. The jobparameters are stored in the JCLLIB/JCLSYS or JMDLIB/JMDSYS in the element whichfollows the job. AVAS inserts a record containing a separator string between the fields, asa separator. This separator string can be defined by the AVAS administrator at generationtime. If no parameters are being used, the separator string is the last record in the element.The separator string must be specified by the user if SV jobs created outside the AVASsystem are to be imported into the AVAS system with COPY-ELEMENT.

The two areas (SV job and job parameters) can be edited using the statements EDIT/SHOW-JOB, EDIT/SHOW-PROD-JOB and MODIFY-SUBMIT-JOB. In EDT, the displayuses workfiles 0 and 1.

The parameters are specified by ‘parametername=’When doing this, note the following:

– The parameter name must always start in column 1, may consist of 1-8 characters, andthis string must not contain any blank characters. It must end with “=”.

– AVAS variables identified by the key fields P#nnn, N#nnn, F#nnn and S#nnn can beused in the job parameter area.

– Statements which have a blank or * in column 1 are not processed during the modifi-cation routine (comments).

– If an arbitrary text item (comment) is specified, it must start with an *. There must be ablank between parametername= and *text.

In the job or net modification routines (CREATE-PROD-JOB/NET), only the job parameterarea is processed. The SV job itself is copied unmodified into the JMDLIB.

For parameters, the format of value assignment and storage is as follows:

JCLLIB JMDLIB

parametername= parametername=assigned value

S#nnn= S#nnn=value of S#nnn

parametername=S#nnn

applies only to AVAS variableswith the key S#nnn

parametername=value of S#nnn

82 U5184-J-Z125-7-76

AVAS variables

Values can be assigned using

– the USER-PARAM-FILE (net/job)

– a net parameter (an AVAS variable from the net masks)

– a job parameter (an AVAS variable from the job masks)The user mask assignment is effected by the #AVM# statement in AVAS.#AVM# is processed only in the job parameter area.

– a system parameter.

In addition, JCL elements (#AVS# and #AVD# statements) can be called in the SV job area(not in the parameter area).

During modification of job parameters a search is also made for parameter names which donot satisfy the naming conventions for F#nnn, N#nnn and P#nnn.In the case of mask parameters (net parameters and job parameters), REM must be usedto assign the parameter name to a mask field. For system parameters, the user mustspecify in addition the S#nnn parameter name, or its name as modified during generation.

During the modification, the value assignments for the specified parameters are sought inthe following areas in the order given:

– area containing the variables from the USER-PARAM-FILE (job)– area containing the variables from the job mask– area containing the variables from the net masks– area containing the variables from the USER-PARAM-FILE (net).

If a variable name is used more than once in the various areas (job mask, net mask andUSER-PARAM-FILE), the value of the first variable found (according to the search process)is used.

Note

With SV jobs, the parameters are converted as follows:

– the passwords are prefixed by a “–“– the equals signs are replaced by blanks– the individual parameter lines are separated by blanks– the order of the parameters is retained.

Example

Like all jobs managed by AVAS, the server job is stored in the JCLLIB of the AVAS config-uration on the BS2000 side. Command sequences and the parameters can be edited usingEDIT-JOB. These are then displayed using EDT in the workfiles 0 (command sequence)and 1 (parameters).

U5184-J-Z125-7-76 83

AVAS variables

A server job (for the Reliant UNIX platform) may look like this:

The value of the parameters n and j is assigned using the AVAS system variables. The usermust assign a value to the parameters h and t, for example, using the USER-PAR-FILE. Thesystem variable S#005 can only be used if the job name was entered in the net structurewithout the user group ($ug_) because $ is a reserved character for parameter values.

When CREATE-PROD-NET is used, the values are assigned to the parameters, and thecommand sequence and the parameters with the value assignments are stored in anelement of the JMDLIB.

In the case of SHOW-PROD-JOB, the information is again displayed using EDT in theworkfiles 0 and 1.

Command sequence(0): echo "START AVAS job: $6"echo " from net: $4"......find /home/avas/list -ctime +$8 -print -exec rm {}\;......echo "Log file to processor $2"......ftp...........$2..............echo "End of job"

Parameter area(1): h= * Name of the AVAS hostn=S#011 * Net namej=S#005 * Job namet= * Specification of days

USER-PAR-FILE: h=D011ZE12t=14

Workfile 0: Workfile 1:

echo "START AVAS job: $6"echo " from net: $4"......find /home/avas/list -ctime +$8 -print -exec rm {}\;......echo "Log file to processor $2"......ftp...........$2..............echo "End of job"

H=D011ZE12n=netcheckj=jobdelt=14

84 U5184-J-Z125-7-76

AVAS variables

If the server jobs are started on the corresponding host (using AVSSTRT), the call with allthe transferred parameters looks like this:

pathname(svjob) -h D011ZE12 -n netcheck -j jobdel -t 14

It is important to note that when an empty string (' ') is assigned to a name (-name), all theparameters following this are moved.Parameter values that begin with the character $ are interpreted and possibly modified bythe system before being transferred to the program (in this case svjob).

The following job is then run:

echo "START AVAS job: jobdel"echo " from net: netcheck"......find /home/avas/list -ctime +14 -print -exec rm {}\;......echo "Log file to processor D011ZE12"......ftp ........... D011ZE12..............echo "End of job"

with the parameter assignment $0 --> pathname(svjob)$1 --> -h$2 --> D011ZE12$3 --> -n$4 --> netcheck$5 --> -j$6 --> jobdel$7 --> -t$8 --> 14

U5184-J-Z125-7-76 85

Runtime logs

3.2.3 Transferring runtime logs to AVAS

The runtime logs of jobs or S procedures started by the AVAS run control system can bebrought together under AVAS and stored in a central library. Runtime logs of SV jobs cannotbe collected.

Two programs, which have to be integrated into the job, are provided for transferring theruntime logs to AVAS:

– The SIGNAL program tells AVAS that a log is to be transferred, and

– the TRANSFER program transfers the job from the user’s work area into AVAS.

The DCAM application CENTRAL has been added to the AVAS system. CENTRAL takesthe log and stores it in the log library (AVAS pool).The dialog statement and the BATCH statement ADD-JOB-LOG are provided for the subse-quent storage of selected logs.

A maximum of 99 logs can be selected and stored for each job.

The logs can be displayed using the statements SHOW-JOB-LOG, SHOW-NET-STATUSand SHOW-JOURNAL.

Logs can be saved and deleted as part of a reorganization exercise. Individual logs can alsobe deleted by the dialog statement or the BATCH statement DELETE-JOB-LOG.

Collecting the logs

A DCAM application is provided for storing the logs while the job is in progress. The appli-cation consists of several inter-communicating DCAM programs. The programs SIGNALand TRANSFER notify the main task, CENTRAL, that logs are available and transfer themto the central library respectively.

CENTRAL tasks

CENTRAL is a shareable DCAM application.It consists of a primary task and a specific number of secondary tasks. The primary taskprovides the central DCAM task resources and controls the application.The secondary tasks handle requests from the DCAM programs and store the logs in thecentral library.In addition to the central access tasks (ZDs), the CENTRAL task, which runs on the samecomputer under the same user id., is started by the ENTER call. CENTRAL is logged underthe ZDs as a special task (similar to AVAK).

86 U5184-J-Z125-7-76

Runtime logs

SIGNAL program

SIGNAL is a non-shareable DCAM program.SIGNAL is loaded as the first program in an AVAS job, immediately after the LOGONstatement and ASSIGN-SYSOUT allocation. It identifies the AVAS job from the task jobvariable and the name of the file containing the SYSOUT data and sends them toCENTRAL, along with other control parameters. SIGNAL logs any problems that occur inprogram job variables.If additional logs (e.g. SYSLST) are to be stored centrally, the SIGNAL program must becalled for each one.

TRANSFER program

TRANSFER is a non-shareable DCAM program.It is either loaded into the AVAS job as the last program, immediately before the LOGOFFstatement, or is started by AVAS as a program and job in its own right.TRANSFER identifies the AVAS job from the task job variable and sends it to CENTRAL,along with any other parameters that may have been specified. If this data is correct,CENTRAL attempts to transfer the log in directly. If this is not possible, CENTRAL requeststhe TRANSFER program to transfer the data in the log. Any problems that occur in theTRANSFER program are logged in a program job variable.

U5184-J-Z125-7-76 87

Runtime logs

Transfer of runtime logs to AVAS

Restrictions

The log records must not exceed the maximum length of the software being used.This means that AVAS can enter log records with a maximum length of 2028 bytes in thelog library. Using EDT, on the other hand, the SHOW functions can only display records thatare 256 bytes in length. If a record is longer, the current function terminates with an error.

OUT-FILE

p r i m a r y - - - - - - - - - secondary 1 - - - - - - - - - secondary 2 - - - - - - - - - secondary n

C

E

N

T

R

A

L

“AVAS job“ :/ASSIGN-SYSOUT/. . SIGNAL/ NAME=OUT-FILE :/ . . TRANSFER :/LOGOFF- - - - - - - - - - - - - -“AVAS job sequence“ :/ . . TRANSFER:/LOGOFF

ABLDAT ZDUPAM

ZDPLAM

AVASpool

88 U5184-J-Z125-7-76

SIGNAL program Runtime logs

Starting and terminating the SIGNAL program

Starting the SIGNAL program

The SIGNAL program must be loaded in an AVAS job, for which it requires a task jobvariable. It gathers all the information required to transfer a log and sends it to theCENTRAL task. SIGNAL may be called several times within the same job, though using thesame log name will result in an error. The log records of the first selected file for a job canbe called up and displayed in the function SHOW-NET-STATUS or SHOW-JOURNAL.

The SIGNAL program is started by calling the procedure AVAS.SIGNAL or from within anAVAS job by a procedure (or command sequence) written by the user. AVAS.SIGNAL is anelement of type J in the SYSPRC.AVAS.040 library.

The following parameters for controlling program execution can be specified throughSTSDTA.

APPLICATION={(ptnname,proname) | jobvariable}

=(ptnname,proname)ptnname is the application name for the CENTRAL task. pronameis the processor name for the CENTRAL task.

=jobvariable The application name of the CENTRAL task starts at position 1 ofthe specified job variable, the processor name at position 9.

The APPLICATION parameter must be specified.

FILE-NAME={*STD | file name}

=*STD The file name for the SYSOUT log is determined by SIGNAL. If nofile name has been allocated to SYSOUT, the SIGNAL programterminates with an error.

Within a job, the SIGNAL program is to be called immediately afterSYSOUT has been passed a file name. Note that any data specifiedbefore the file name assignment will not be entered in the file.

=file name Specifies the name of the log file to be passed to CENTRAL. Thisenables any SAM or ISAM file (minus the index key) to be trans-ferred.

Note

This parameter is only required in cases where a log file different tothe one specified with /ASSIGN-SYSOUT is to be collected.

U5184-J-Z125-7-76 89

Runtime logs SIGNAL program

TRANSFER-OPTION={ENDED | ERROR | NO}

=ENDED The run control system starts a follow-up job to transfer this log if thelog was not transferred during execution of the job by a call toTRANSFER.The error-free transmission of this log is not a precondition for thenormal termination of the job in the AVAS system.The job status is not affected by the outcome of the log trans-mission.

=ERROR The run control system starts a follow-up job to transfer this log if thelog was not transferred during execution of the job by a call toTRANSFER.The error-free transmission of this log is a precondition for thenormal termination of the job in the AVAS system.A job status of ERROR is returned if the log could not be transferred.A restart should be initiated for the net/job in such cases.

=NO The run control system does not start a follow-up job to transfer thislog.If the log was transferred during the job, users must flag normal orabnormal job termination themselves, and thus the status of the jobin AVAS, by evaluating the return codes for the job.

Note

If the TRANSFER-OPTION parameter is not present, the valuespecified when CENTRAL was started will be used.

The run control system does not start a follow-up job in the case oflogs that the system attempted to transfer during the job but wasunable to do so because of an error.

If transfer of a log is abandoned as the result of an error, any datatransferred up to that point will not be saved.An ERROR status is allocated to that log in the log directory.

If several logs with different TRANSFER-OPTIONs are flagged,they will be treated differently accordingly.

90 U5184-J-Z125-7-76

SIGNAL program Runtime logs

DELETE={YES | NO}The DELETE parameter is only to be specified with SIGNAL whenseveral logs are flagged and the files are to be handled differentlyfollowing successful transmission and TRANSFER is called up bythe run control system in a follow-up job.The files are deleted by TRANSFER.

=YES The file is to be deleted after the data has been successfully saved.

=NO The file is retained under the new user ID.

Note

If the DELETE parameter is not present, the value specified whenCENTRAL was started will be used.This value can still be modified from the TRANSFER program.

Terminating the SIGNAL program

The SIGNAL program terminates when all data has been sent to the CENTRAL task.If errors occur during the SIGNAL program (e.g. incorrect parameter specified, CENTRALtask not available, etc.), a message is output. If a program job variable was specified whenSIGNAL was started, the message number (minus AVS) will be entered in the return codeindicator field of the program job variable.

Problems during the execution of SIGNAL must result in an entry in the task job variable(see page 70) or must terminate a job abnormally, so that the status ERROR is set in thenet structure element.

Notes

– If a job has several logs, the JOBLOG operation in the SHOW-NET-STATUS andSHOW-JOURNAL functions will only display the first log. It therefore makes sense toflag the file designated by the ASSIGN-SYSOUT statement as the first file.

– Tasks with TYPE=EXX can only use the SIGNAL program if the external monitoring jobvariable can be addressed as a task job variable via the file link name *SMONJVJ.

U5184-J-Z125-7-76 91

Runtime logs TRANSFER program

Starting and terminating the TRANSFER program

Starting the TRANSFER program

The TRANSFER program transfers logs to the CENTRAL task, for which it requires a taskjob variable. Transfer takes place in the same job or a follow-up job.To transfer the log in the same job, the procedure AVAS.TRANSFER or a procedure (orcommand sequence) written by the user is included in the AVAS job.AVAS.TRANSFER is an element of type J in the SYSPRC.AVAS.040 library.Transfer from a follow-up job is controlled by the TRANSFER-OPTION parameter in theSIGNAL program.

The following parameters for controlling program execution can be specified throughSTSDTA.

APPLICATION={(ptnname,proname) | jobvariable}

=(ptnname,proname)ptnname is the application name for the CENTRAL task. pronameis the processor name for the CENTRAL task.

=jobvariable The application name of the CENTRAL task starts at position 1 ofthe specified job variable, the processor name at position 9.

The APPLICATION parameter must be specified.

FILE-NAME={*ALL | *LAST | file name}

=*ALL All logs flagged by the SIGNAL program are to be transferred.

=*LAST The most recently flagged log is to be transferred. The log not yetprocessed by TRANSFER at this time is the one that will be trans-ferred.

=file name Name of a log file.The name of the log must be flagged and consequently known to theCENTRAL task.

Note

The default value of the parameter is *ALL.The default value can be modified in the CENTRAL task to *LAST.

92 U5184-J-Z125-7-76

TRANSFER program Runtime logs

DELETE={NO | YES}

=NO The file is retained under the new user ID.

=YES The file is to be deleted after the data has been successfully saved.

Note

If the DELETE parameter is not present, the value specified whenSIGNAL was started or the value specified by CENTRAL will beused.The DELETE value set by TRANSFER supersedes the one set bySIGNAL.

Terminating the TRANSFER program

The TRANSFER program terminates once it has sent all information and data to theCENTRAL task.If errors occur during the TRANSFER operation (e.g. incorrect parameter specified,CENTRAL task not available, file READ password-protected, etc.), a message is output. Ifa program job variable was specified when TRANSFER was started, the message number(minus AVS) will be entered in the return code display field of the program job variable.

Problems during the execution of TRANSFER must result in an entry in the task job variable(see page 70) or must terminate a job abnormally, so that the status ERROR is set in thenet structure element.

Note

Tasks with TYPE=EXX can only use the TRANSFER program if the external monitoringjob variable can be addressed as a task job variable via the file link name *SMONJVJ.

U5184-J-Z125-7-76 93

Runtime logs Control parameters

Notes on the control parameters

Parameters for controlling the execution of SIGNAL and TRANSFER are specified viaSYSDTA when the programs are started. The default values for these control parametersare selected to provide a simple way of compiling the data required for a log. These param-eters also provide a way of transferring further SAM or ISAM files into the central AVAS poolso that the production of jobs in the computer center is as complete as possible and notsusceptible to change.

Notes on the control parameters

FILE-NAME= with the TRANSFER programThis parameter is necessary when only one log is to be compiled, even though anumber have been flagged. Specifying a name permits a 1 to 1 relationship betweenSIGNAL and TRANSFER to be established.The value *LAST allows a job to be controlled on the "last in – first out" principle. Thisprinciple can still be applied even if an error occurs in the TRANSFER program.

FILE-NAME=*ALL is always used if the TRANSFER program is started by the runcontrol system as a follow-up job.

TRANSFER-OPTION with the SIGNAL programThe transfer of the logs flagged by SIGNAL during an AVAS job can be performed byissuing a TRANSFER call in the AVAS job or by the run control system starting a follow-up job that includes a TRANSFER call. As a rule, the run control system checks whetherTRANSFER was started from the AVAS job and starts a follow-up job if this is not thecase. The user does not have to give this follow-up job any special attention as far asthe AVAS net structure is concerned.

If TRANSFER-OPTION=NO is specified,the start of a follow-up job for the transmission of logs can be inhibited, irrespective ofwhether TRANSFER was called in the AVAS job or not.If TRANSFER was called from the AVAS job and errors occurred during the transfer, theuser can evaluate the return codes to determine whether the job terminated normallyor abnormally.The flagged logs can be subsequently brought together using the ADD-JOB-LOGstatement.If TRANSFER was not called from the AVAS job and an error occurred while transferringa log, the TRANSFER-OPTION parameter can be used to decide whether or not theerror is to affect the job status.

If TRANSFER-OPTION=ENDED is specified,the job status is not affected when an error occurs during transfer of a log. The statusset when the AVAS job terminates is the only one that counts as far as the job status isconcerned.

94 U5184-J-Z125-7-76

Control parameters Runtime logs

If TRANSFER-OPTION=ERROR is specified,the job status ERROR will be set if an error occurs while transferring a log. A job statusof ENDED will only be reached when the AVAS job terminates normally and the flaggedlogs have been successfully transferred.

DELETE=NO | YES in the SIGNAL and TRANSFER programsThis parameter determines whether log files are deleted following the successfultransfer of a log.If the parameter is not specified with either SIGNAL or TRANSFER, the default valuespecified when the CENTRAL task was started will be used. If the parameter is notspecified with SIGNAL, the default value for the CENTRAL task will be used.If the parameter was specified with TRANSFER, the value specified with SIGNAL willbe overwritten.

U5184-J-Z125-7-76 95

Editing jobs, S procedures, server jobs and JCL elements EDIT-JOB

3.3 Editing jobs, S procedures, server jobs and JCL elements

Under AVAS, jobs, S procedures, SV jobs and JCL elements which are stored in the AVASuser library JCLLIB can be edited using EDIT-JOB. External jobs and S procedures, i.e.those outside the AVAS environment, can only be edited using the EDT statement. Theycan be copied to the JCLLIB using COPY-ELEMENT (see page 207). External SV jobs canbe edited on their respective systems using an editor, or they must be imported onto theAVAS host and copied to the JCLLIB with COPY-ELEMENT. Elements in the JCLLIB canbe edited with the statements below.

Overview of statements

EDIT-JOBEdit jobs, S procedures, server jobs and JCL elements

As an element in the JCLLIB, a job, an S procedure, an SV job or a JCL element can eitherbe addressed directly via the ELEMENT-NAME operand, or be selected by marking theelement name in the AVE010 mask. This mask presents an overview of existing elements,and is displayed when the statement is specified without operands or when a selection ismade via a partially qualified element name.The overview only contains elements belonging to the specified user group or to the user’sown user group; only privileged users are allowed to edit elements belonging to a foreignuser group.

The selected element is displayed on the screen in EDT, and can be edited with EDT state-ments.

The EDT display differs for a job, an S procedure and an SV job.The job, SV job, JCL element or S procedure is output using workfile (0) in EDT. The param-eters of an SV job or an S procedure are output using workfile (1) in EDT, which is the onlyplace where they can be created or prepared.

If an element which already exists is being edited, a message informs the user whether it isa job, an SV job or an S procedure (only if this has previously been specified by the uservia the parameter field FUNCTION= in mask AVE011).

EDIT-JOB Edit jobs, S procedures, server jobs and JCL elements (with EDT)

SHOW-JOB Display jobs, S procedures, server jobs and JCL elements (via EDT)

DELETE-JOB Delete jobs, S procedures, server jobs and JCL elements

EDT Edit external SAM/ISAM user files (with EDT)

96 U5184-J-Z125-7-76

EDIT-JOB Editing jobs, S procedures, server jobs and JCL elements

Once the user has terminated EDT processing, the AVE011 mask is displayed. The usercan now decide whether to

– write the modified element back to the JCLLIB or

– write the element back not as a job, but as an S procedure (or a procedure element)

– enter it in the JCLLIB under a new name as a job, an S procedure or an SV job (or asa job/procedure/SV element), i.e. copy it.

An attempt to overwrite an S procedure or an SV job with a job of the same name is imper-missible, and will be rejected with a corresponding message.Also not permitted is the overwriting of an S procedure or a job with an SV job of the samename and vice versa.

If the modified element is to be written back, OVERWRITE=YES and the SAVE operationmust be specified.If the modified element is to be entered with a new name, the new element name, the SAVEoperation and OVERWRITE=YES (if the new element name already exists) must bespecified in the AVE011 mask.

Depending on whether the element is to be saved as a job, an SV job or an S procedure,either the parameter FUNCTION=J, FUNCTION=X or FUNCTION=P must be specified,respectively. Only if FUNCTION=X or FUNCTION=P is specified will the server job param-eters or the procedure parameters (EDT display, workfile (1)) be written back.

If two or more elements were selected in the element overview (AVE010) prior to EDTprocessing, these elements are displayed consecutively in EDT for editing and subsequent"saving" (SAVE).

If an edited element is not to be written back to the JCLLIB, element editing can be abortedby entering the RETURN operation in mask AVE011. The next marked element is thendisplayed for editing in EDT, or, alternatively, the AVE010 overview mask is displayed.

ELEMENT-NAME=Name of a job, an S procedure, an SV job or a JCL element in the JCLLIB.

ELEMENT-NAME=$ug_Name of the user group.Only privileged users (see "AVAS for the Administrator" [3]) are allowed to specify a"foreign" user group. If no user group is specified, the elements belonging to the user’s ownuser group are displayed.

EDIT-JOB

[ELEMENT-NAME=[$ug_ ]element]

U5184-J-Z125-7-76 97

EDIT-JOB Mask AVE010

ELEMENT-NAME=elementElement name in the JCLLIB.This entry directly causes the element to be edited in EDT.

If the element name is entered via a partial qualification (final character *), an overview isdisplayed of those elements whose names begin with the partial qualification.

If no element name is entered, all elements of the specified user group are displayed.

AVE010 - Overview mask of jobs, S procedures, SV jobs and JCL elements

AVAS-USER-LIBRARYOutput parameter.Abbreviated name of the processed AVAS library: JCLLIB.

DATE Output parameterDate of last modification.

ELEMENT-NAME Output parameter.Names of the jobs, S procedures, SV jobs and JCL elements.

F Output parameter.The function of the element.Attribute which distinguishes between a job, an S procedure and anSV job.

J (Job) The element is created as a job or as a JCL element for jobs.

P (Procedure) The element is created as an S procedure or as a JCL element forS procedures.

X (SV job) The element is created as an SV job or as a JCL element for SVjobs.

Note

If no value is displayed in the parameter field, the element is inter-preted as being a job. In mask AVE011, the user must specify eitherFUNCTION=J, FUNCTION=X or FUNCTION=P before the elementcan be saved with the CMD:SAVE.

M Input parameter.

S (Select) This selects an element for editing in EDT.

RESULT Output parameter.

NEWGEN The element was entered in the JCLLIB with a new name. Theedited element is retained in the JCLLIB in its original state andunder its original name. The element with the new element namedoes not appear in the overview mask until a later display.

98 U5184-J-Z125-7-76

Mask AVE011 EDIT-JOB

UPDATED The element was written back.

NO-UPDATE The element was not saved (e.g. element editing was aborted withRETURN).

AVE011 - Display after terminating EDT

AVAS-USER-LIBRARYOutput parameter.Abbreviated name of the processed AVAS library: JCLLIB

ELEMENT-NAME Output parameter.Name of the edited job or JCL element.

FUNCTION Input/output parameterThe function of the element.Attribute which distinguishes between a job, an S procedure and anSV job.

J (Job) The element is to be recorded as a job or as a JCL element for jobs.

P (Procedure) The element is to be recorded as an S procedure or as a JCLelement for S procedures.

X (SV job) The element is to be recorded as an SV job or as a JCL element forSV jobs.

Note

The value assigned to the element which is being edited will bedisplayed. If no value has yet been assigned for the element whichis being edited, the value J will by default be inserted in theparameter field. This predefined value can be overwritten.

NEW-ELEMENT-NAMEInput/output parameter.Name of the new element, with which it is to be entered in theJCLLIB.

OVERWRITE=NO Input/output parameter.{YES | NO}

By default, the value NO will be output, unless the system param-eters have been used to set YES as the default value.

The preset value NO must be overwritten by YES and the SAVEoperation specified if:

– an edited element is to be written back to the JCLLIB;

U5184-J-Z125-7-76 99

EDIT-JOB Mask AVE011

– the edited element is to be transferred to the JCLLIB with a newname and the name specified for NEW-ELEMENT-NAMEalready exists in the JCLLIB. The contents of the existingelement are overwritten in the process.

Notes

– Empty elements cannot be saved. In EDT, the workfile (0) must contain entries for jobs,S procedures and SV jobs, or else the SAVE operation will be rejected with a message.

– If an element is to be written back as an S procedure or an SV job, a separator string isalso saved in the element. If parameters are being used, the separator string is insertedinto the element as a record between the procedure part or SV job (workfile(0)) and theprocedure parameters or server job parameters (workfile(1)). If there are no parameters(workfile (1) empty), the separator string will be stored as the last record in the element.The separator string is not included in the output when editing with EDT.

100 U5184-J-Z125-7-76

SHOW-JOB Editing jobs, S procedures, server jobs and JCL elements

SHOW-JOBDisplay jobs, S procedures, server jobs and JCL elements

This statement can be used to display jobs, S procedures, SV jobs and JCL elements fromthe JCLLIB or JCLSYS. The contents of the individual elements are displayed on the screenby EDT. Although all EDT update functions are possible, the modified contents cannot bewritten back to the JCLLIB. Even changing from SHOW-JOB to EDIT-JOB causes themodifications to be lost, since in this case the element is reread from the library before theSAVE operation can be entered.

The PRINT operation enables the elements to be output in a LIST file.

Elements are selected for display or output to a LIST file by flagging them with S or Y marksrespectively.

ELEMENT-NAME=Name of a job, an S procedure, an SV job or a JCL element in the JCLLIB or JCLSYS.

ELEMENT-NAME=$ug_Name of the user group.Only privileged users are allowed to specify a foreign user group.If the system user group $ugsys is specified, the JCLSYS is searched; otherwise theJCLLIB is searched. If no user group is specified, all elements belonging to the user’s ownuser group are displayed.

ELEMENT-NAME=elementElement name in the JCLLIB or JCLSYS.This entry directly causes elements to be displayed in EDT.


If no element name is entered, all elements belonging to the specified user group aredisplayed.

SHOW-JOB


U5184-J-Z125-7-76 101

SHOW-JOB Mask AVE010

AVE010 - Overview mask of jobs, S procedures, SV jobs and JCL elements

AVAS-USER-LIBRARYOutput parameter.Abbreviated name of the processed AVAS library: JCLLIB orJCLSYS.



F Output parameter.The function of the element.Attribute which distinguishes between a job, an SV job and an Sprocedure.

J (Job) The element is created as a job or JCL element.

P (Procedure) The element is created as an S procedure or as a procedureelement.

X (SV job) The element is created as an SV job or an SV element.

M Input parameter.

S (Select) This selects an element to be displayed in EDT. The elements aredisplayed in EDT by performing the EXECUTE operation.

Y (Yes) The selected element is to be output to a LIST file.

The mark N is not permitted in this instance.

RESULT This parameter is irrelevant here.

102 U5184-J-Z125-7-76

DELETE-JOB Editing jobs, S procedures, server jobs and JCL elements

DELETE-JOBDelete jobs, S procedures, server jobs and JCL elements

The DELETE-JOB statement enables the user to delete jobs, S procedures, SV jobs andJCL elements from the AVAS user library JCLLIB.

ELEMENT-NAME=Name of a job, an S procedure, an SV job or a JCL element in the JCLLIB.

ELEMENT-NAME=$ug_Name of the user group.Only privileged users are allowed to specify a foreign user group. If no user group isspecified, the elements belonging to the user’s own user group are displayed.

ELEMENT-NAME=elementElement name in the JCLLIB.This entry causes the element to be displayed in the overview mask.


If no element name is entered, all elements belonging to the specified user group aredisplayed.

Notes

– If the statement is issued without operands, all the elements belonging to the user’s ownuser group are presented for deletion.

– Jobs, SV jobs, S procedures and JCL elements from the JCLSYS can only be deletedby the AVAS administrator (see "AVAS for the Administrator" [3]).

DELETE-JOB


U5184-J-Z125-7-76 103

DELETE-JOB Mask AVE010

AVE010 - Overview mask for jobs, S procedures, SV jobs and JCL elements

AVAS-USER-LIBRARYOutput parameter.Name of the processed AVAS library: JCLLIB.



F Output parameter.The function of the element.Attribute which distinguishes between a job, an SV job and an Sprocedure.

J (Job) The element is created as a job or job element.

P (Procedure) The element is created as an S procedure or a procedure element.

X (SV job) The element is created as an SV job or SV element.

M Input parameter.

Y (Yes) The marked element is to be deleted.


DELETED The element was deleted from the JCLLIB.

LOCKED The element could not be deleted because it is currently beingedited by another user.

104 U5184-J-Z125-7-76

EDT Editing jobs, S procedures, server jobs and JCL elements

EDTEdit external SAM/ISAM user files

In order to make it easier for the user to edit user files outside the AVAS environment, it ispossible to call EDT under AVAS.

This statement is not allowed to have any operands. This means that any entries in the OPRfield from a preceding statement must be deleted. Once EDT has been called, it is notpossible to edit elements in the AVAS libraries.

Once EDT has been terminated by means of HALT, control automatically returns to AVASand the empty system mask AVS030 is displayed.

If the edited files are not saved, then when EDT is terminated a corresponding message willbe output. AVAS branches back into EDT for the user to perform the save. If EDT is termi-nated again at this point, there will be an unconditional return to AVAS.

EDT

U5184-J-Z125-7-76 105

Editing documentation elements

3.4 Editing documentation elements

Documentation elements are stored in the documentation library DOCLIB and can beedited, displayed and deleted by means of the following statements.


The elements are displayed and edited using EDT.For this purpose, EDT is called such that the documentation can be displayed and enteredin uppercase and lowercase letters.

If the ELEMENT-NAME operand is specified in the statements, either one element or adirectory of all the elements from the documentation library DOCLIB is displayed. The formof partial qualification specified for the element name determines what is displayed.Individual elements can be selected for editing with mark S or Y.

Editing of documentation elements by way of the ELEMENT-NAME operand has no effecteither on the assignment of the documentation elements to the nets or to the specificationsin the net.

The documentation elements are assigned to the condition descriptions in the ADD-COND-DESCRIPTION and MODIFY-COND-DESCRIPTION statements.

The documentation elements are assigned to the nets and to the structure elements of thenets with the CREATE-NET-DESCRIPTION and MODIFY-NET-DESCRIPTION statements.

Elements from the system documentation library DOCSYS can be displayed by means ofthe SHOW-DOCUMENT statement if the element name is specified with $ugsys.

EDIT-DOCUMENT Edit documentation elements

SHOW-DOCUMENT Display documentation elements

DELETE-DOCUMENT Delete documentation elements

106 U5184-J-Z125-7-76

EDIT-DOCUMENT Editing documentation elements

EDIT-DOCUMENTEdit documentation elements

The EDIT-DOCUMENT statement is used to select documentation elements from theDOCLIB and display them by way of masks for editing. Depending on the operand andoperand value entered, the following masks are output:

ELEMENT-NAME=Name of a documentation element in the DOCLIB whose records are to be displayed forediting by EDT.

ELEMENT-NAME=$ug_Name of the user groupIf no user group is specified, the elements from the user’s own user group are output.Only a privileged user may specify a foreign user group.

ELEMENT-NAME=elementName of the documentation element in the DOCLIB.Results directly in editing of the documentation element by EDT. Mask AVS016 is subse-quently output.

If the element name is specified in partially qualified form (last character *), this producesan overview of all documentation elements whose names begin with the partial qualification(mask AVS019).

Note

If the statement is issued without operands, all documentation elements with the usergroup of the user executing the function are displayed (mask AVS019).

ELEMENT-NAME=partially qualified

AVS019 - Overview of documentation files

ELEMENT-NAME=fully qualified

Displays the data records of the documentation elementsthrough EDT

no operandspecified

AVS019 - Overview of documentation files for own user group

EDIT-DOCUMENT


U5184-J-Z125-7-76 107

EDIT-DOCUMENT Masks AVS019/AVS016

AVS019 - Overview of the documentation files

Mask AVS019 is output only if the ELEMENT-NAME operand is specified in partiallyqualified form or if no operand is specified.

DATE Output parameterVersion date of the documentation element in the documentationlibrary DOCLIB.yyyy-mm-dd

DOCUMENT-NAME Output parameterNames of the documentation elements presented for modification.

M Input parameter

S (Select) The marked documentation element is selected for modification.

Following the EXECUTE operation the records of this documen-tation element are displayed for editing with EDT.

RESULT Output parameterConfirmation of the action performed.

UPDATED The documentation element has been modified in the DOCLIB.

NO-UPDATE The documentation element has not been modified in the DOCLIB(RETURN operation).

NEWGEN The documentation element has been entered in the DOCLIB undera new name. The element indicated by RESULT has not beenmodified.The element with the new element name will be displayed only in asubsequent output of the overview mask.

AVS016 - Output on termination of EDT

DOCUMENT-NAME Output parameterName of the edited documentation element.

NEW-DOCUMENT-NAMEInput parameterName of the new documentation element under which it is to beentered in the DOCLIB.$ug_elementname

OVERWRITE Input parameter

YES An existing element having the same name is to be overwritten.

NO An existing element having the same name is not to be overwritten.

108 U5184-J-Z125-7-76

SHOW-DOCUMENT Editing documentation elements

SHOW-DOCUMENTDisplay documentation elements

The SHOW-DOCUMENT statement is used to display documentation elements by way ofEDT. They can be output to a LIST file by means of the PRINT operation.The elements are selected by the S mark for display and by the Y mark for output to a LISTfile.

Depending on the operand and operand value entered, the same masks are output as withEDIT-DOCUMENT (see page 106).

ELEMENT-NAME=Name of a documentation element in the DOCLIB or DOCSYS whose records are to bedisplayed for editing through EDT.

ELEMENT-NAME=$ug_Name of the user groupIf a documentation element from the DOCSYS is to be displayed, $ugsys_ must bespecified.

If no user group is specified, the elements from the user’s own user group are displayed.

Only a privileged user may specify a foreign user group.

ELEMENT-NAME=elementName of the documentation element in the DOCLIB.Results directly in display of the documentation element through EDT. On returning fromEDT, system mask AVS030 is output.


Note


SHOW-DOCUMENT


U5184-J-Z125-7-76 109

SHOW-DOCUMENT Mask AVS019


The parameters for mask AVS019 are described under the EDIT-DOCUMENT statement.The RESULT parameter has no significance here. The documentation elements can beselected in the mark column.

M Input parameter

S (Select) The marked documentation element is selected for display.Following the EXECUTE operation the records of this documen-tation element are displayed for editing with EDT.

Y (Yes) The marked documentation element is to be output to a LIST file.

The N mark is not permitted here.

110 U5184-J-Z125-7-76

DELETE-DOCUMENT Editing documentation elements

DELETE-DOCUMENTDelete documentation elements

The DELETE-DOCUMENT statement is used to delete documentation elements from theDOCLIB.

The deletion of documentation elements via mask AVS019 has no effect on the assignmentof the documentation elements in the net.

Elements in the system documentation library DOCSYS can be deleted by means of theDELETE-SYSTEM-ELEMENT statement, operand AVAS-SYSTEM-LIB=DOCSYS.

ELEMENT-NAME=Name of a documentation element in the DOCLIB, that is to be deleted.

ELEMENT-NAME=$ug_Name of the user groupIf no user group is specified, the elements from the user’s own user group are output.

Only a privileged user may specify a foreign user group.

ELEMENT-NAME=elementName of the documentation element in the DOCLIB.Results in display of the element name in the overview mask AVS019.


Note


DELETE-DOCUMENT


U5184-J-Z125-7-76 111

DELETE-DOCUMENT Mask AVS019


DATE Output parameterVersion date of the documentation element in the documentationlibrary DOCLIB.yyyy-mm-dd

DOCUMENT-NAME Output parameterNames of the documentation elements presented for deletion.

M Input parameter

Y (Yes) The marked documentation element is to be deleted.


DELETED The documentation element has been deleted from the DOCLIB.

NO-DELETE The documentation element does not exist or the element does notconform to AVAS conventions.

LOCKED The element is locked at present.

ERROR An error occurred while accessing the element or library.

112 U5184-J-Z125-7-76

Editing nets

3.5 Editing nets

As a rule, net descriptions have the following format:

Description of the net parameters (mask AVN001)

Description of the net plan data (mask AVN020)

Format specifications for user masks (mask AVN006)

Net structure description (mask AVN004)

with structure elementsfor starting a job, an SV job or an S procedurefor defining a condition descriptionfor modifying a condition descriptionfor testing a conditionfor deleting a condition description

The CREATE-NET-DESCRIPTION statement enables the user to create a net descriptionand store it as a net in the net library. Internally, a net description consists of structureelements which must be defined for the net, for each job, S procedure or SV job, and forconditions governing the start of an index level.

For the net, data must be defined for the symbolic and real start times, the net parameters,the default values for the job parameters, and the net masks required for modificationpurposes.

For the structure elements, data must be defined for selecting the structure element(TURNUS and SYMDAT), as must the assigned parameters, depending on the function ofthe structure element.

With the condition descriptions, data must be defined for condition selection (TURNUS,SYMDAT), the condition description (COND-NAME) and the condition value (COND-VALUE).

U5184-J-Z125-7-76 113

Editing nets

All structure elements in a net must be assigned an index, in ascending order according tothe order of net execution. The index sequence may contain gaps.

INDEX

001 : Structure elements for starting jobs, : SV jobs and S procedures : and : for processing and testing : condition descriptions and conditions :899

900 : Structure elements which must be executed : in addition during a restart after an error999

Within a net, a job, an S procedure or an SV job may run more than once on different indexlevels. However, it may only be called once on a given index level.In a net, the same name must not be used for a job, an S procedure or an SV job, otherwisethe CHECK function records an error.The net cannot be planned.

If the start of the first job/SV job or the first S procedure in a net is to be made dependenton external conditions, only these conditions may appear on the lowest index level of thenet. External conditions include: waiting for another net to terminate; waiting for the end ofa job in another net; waiting for the availability of a resource; waiting until a VALUE typecondition description has a preset value; or waiting until a job variable contains a presetvalue.

114 U5184-J-Z125-7-76

Editing nets

3.5.1 Defining jobs, S procedures and server jobs in a net description

A structure element for starting a job, an S procedure or an SV job is described in the netdescription with FUNCTION=J, FUNCTION=P or FUNCTION=X.

The following types of job, S procedure and SV job can be defined in the net description:

MOD– FUNCTION=J/P/X

The job, S procedure or SV job is saved in the AVAS system and is subject to net modifi-cation.It must be created as a temporary task by a CREATE-PROD-NET statement.

STD– FUNCTION=J/P/X

The job, S procedure or SV job is saved in the AVAS system and is not subject to netmodification.The production task must be created by a CREATE-PROD-JOB statement.

EXT– FUNCTION=J/P

The job or S procedure is not saved in the AVAS system and is started under the AVASnet control system by an /ENTER-JOB or /ENTER-PROCEDURE command. The job orS procedure is assigned via the file name specified under ENTER-FILE (see maskAVN002).In the case of external jobs and S procedures, NET must be specified in the ENTER-PARAM parameter field (see mask AVN002).

– FUNCTION=XThe SV job is not saved in the AVAS system; instead it is available in the server system.It is started under the AVAS-SV net control system on the server system. The SV job isassigned via the file name specified under FILENAME (see mask AVN009).In the ENTER-PARAM parameter field (mask AVN009), NET is entered as the defaultvalue and cannot be changed.

EXX– FUNCTION=P

The S procedure is not saved in the AVAS system and is started under the AVAS netcontrol system by an /ENTER-PROCEDURE command. The S procedure is assignedvia the file name specified under ENTER-FILE (see mask AVN002). The contents ofJOB-PARAMETER (mask AVN002) are assigned to the procedure parameters.

The monitoring job variable is not assigned to the S procedure as a task job variable(external S procedure with external monitoring job variable). The run control systemsets up the job variable with an internal name.The job variable is assigned a password according to the start parameters of the runcontrol system.

U5184-J-Z125-7-76 115

Editing nets Defining conditions

The user must give the job variable a value just like with a task job variable. Thecontents are governed by the rules for BS2000 task job variables and for the AVASstatement #AVJ# (setting errors and restart variants via the task job variable).

If the SIGNAL and TRANSFER programs are to run under the external control system,you must make sure that these programs can address the job variable via the file linkname *SMONJVJ.

ENTER-PROCEDUREFROM-FILE=<ENTER-FILE>,PROC-PASS=<FILE-PASSWORD>,MONJV=*NONE,PROCEDURE-PARAMETERS=( CONTROL-JVA-NAME=control-jva-name,CONTROL-JVA-PASSW=control-jva-passw <Contents of JOB-PARAMETER>)

In the case of external S procedures, NET must be specified in the ENTER-PARAMparameter field (see mask AVN002).

3.5.2 Defining conditions in a net description

It is possible to test the following types of conditions in a net description:

Furthermore, the RESOURCE and VALUE conditions can be defined in the net description,so that they are available for use both by the net which defines them and by other nets.

NET / JOB conditions

A NET condition is used to wait for a condition on another net to be satisfied. The other netmay be in the user’s own group or another one.

A JOB condition is used to wait for a condition on a job to be satisfied. The job may belongto the same net or to another one.

Nets and jobs referred to in such dependencies must be identified in the net description viathe LIFE-TIME parameter.

NET condition Satisfaction of a condition on another net

JOB condition Satisfaction of a condition on a job

RESOURCE condition Satisfaction of a condition on a resource

VALUE condition Satisfaction of a condition by a defined value

JVA condition Satisfaction of a condition by a defined value of a job variable

116 U5184-J-Z125-7-76

Defining conditions Editing nets

When either a SUBMIT or REPEAT is executed for the net, a condition description is theninitialized in the run control file, containing the data for the net or job as applicable. Subse-quently, this entry will be given the appropriate status (e.g. the entry is set to the appropriatestatus (ENDED, ERROR,...) after the net or job terminates). If the net or job is omitted, or ifthe job is deleted, the values IGNORED or DELETED will be set.

If dependencies on other nets and jobs are defined in a net, a check will be made at thetime of their execution to determine whether a condition description (already) exists. If thereis already a condition description for the condition (e.g. in the case when a condition onanother net is tested), details of the net which is waiting are noted in the condition. If, on theother hand, no description exists yet, the status NO-OCCURE will be set for the condition.

The descriptions for NET and JOB conditions can be edited in a dialog using the statementsDELETE-/MODIFY/SHOW-COND-DESCRIPTION.

DELETE-COND-DESCRIPTION enables a condition description for a NET / JOB conditionto be deleted.

MODIFY-COND-DESCRIPTION enables the status and the LIFE-TIME of the conditiondescription to be modified.

SHOW-COND-DESCRIPTION allows the user to display the nets which are waiting for aNET / JOB condition to be satisfied, and secondly to output the contents of a conditiondescription (net or job creating it, status of the condition, status of the entry).

In testing a NET or JOB condition, the test will be applied to the net or job which has aPLAN-START before and closest to the PLAN-START of the dependent net.

U5184-J-Z125-7-76 117


RESOURCE conditions

A RESOURCE condition is defined, modified, deleted and tested within the net structure.

A resource can be allocated (exclusively or shared) when it is defined or tested, and it canbe released again using the modify function. A resource in AVAS is a logical construct,defined by the user, for which (only) the user can set up a reference to real BS2000resources, e.g. files.

If a RESOURCE condition is created during the processing of a net, a correspondingcondition description is noted in the run control file. If a RESOURCE condition is tested andthere is not yet a condition description in the run control file, the status NO-OCCURE willbe set for the condition. If there is a condition description in the run control file, the testingof the RESOURCE condition will produce the following results, depending on theassignment status:

– a resource with COND-STATUS = FREE will be allocated in SHARE or EXCLUSIVEmode as appropriate.

– a resource with COND-STATUS = SHARE will be assigned to the additional net inSHARE mode (even if there is an outstanding request for allocation in EXCLUSIVEmode).

– If several nets are waiting for the exclusive assignment of a resource, then when thisresource next has the status FREE it will be assigned to the net which was first torequest its allocation.

The net which tests the condition is noted, with the time of first testing, in the conditiondescription.

The descriptions for RESOURCE conditions can be edited in a dialog using the statementsADD-/MODIFY-/DELETE-/SHOW-COND-DESCRIPTION.

ADD-COND-DESCRIPTION enables a RESOURCE condition to be defined, even outsidea net.

MODIFY-COND-DESCRIPTION enables a RESOURCE condition to be released.

DELETE-COND-DESCRIPTION enables a condition description for a RESOURCEcondition to be deleted.

SHOW-COND-DESCRIPTION allows the user to display the nets which are waiting for aparticular status, and thus a condition to be satisfied, and secondly to output the contentsof a condition description (net or user creating it, status of the condition, status of the entry).

118 U5184-J-Z125-7-76

Defining conditions Editing nets

VALUE conditions

A VALUE condition is defined, modified, deleted and tested in the net structure.

Modification can be used to set a different value. When a VALUE condition is tested, therelationships “equal to”, “not equal to”, “greater than”, “greater than or equal to”, “less than”,“less than or equal to” can be tested. It is also possible to combine two values using a logical“OR”.

If a VALUE condition is created during the processing of a net, a corresponding conditiondescription is noted in the run control file. If a VALUE condition is tested and there is not yeta condition description in the run control file, the status NO-OCCURE will be set for thecondition. If there is a condition description in the run control file with a different value, thetesting net will be noted in this condition description as waiting.

The descriptions for VALUE conditions can be edited in a dialog using the statements ADD-/MODIFY-/DELETE-/SHOW-COND-DESCRIPTION.

ADD-COND-DESCRIPTION enables a VALUE condition to be defined, even outside a net.

MODIFY-COND-DESCRIPTION enables a VALUE condition to be modified.

DELETE-COND-DESCRIPTION enables a condition description for a VALUE condition tobe deleted.

SHOW-COND-DESCRIPTION allows the user to display the nets which are waiting for aparticular value, and thus a VALUE condition to be satisfied, and secondly to output thecontents of a condition description (net or user creating it, status of the condition, status ofthe entry).

Condition control

For each of the condition types, NET, JOB, VALUE and RESOURCE, the user can prescribea value or the OCCURE-VALUE status for which the condition is considered to be satisfied.It is also possible to specify a list of status values for OCCURE-VALUE. In addition, the usercan specify an ERROR-VALUE for any condition, which will cause the condition itself tohave an ERROR status.

As in the case of jobs, it is possible to set three restart variants for the conditions. Onerestart variant can be directly assigned to the ERROR-VALUE (this corresponds to thevariant specified by the MONJV in the case of a job). This means that it is also possible inthe case of conditions to initiate a prescribed restart.

U5184-J-Z125-7-76 119


JVA conditions

A JVA condition waits for the condition to be satisfied by a job variable taking a definedvalue.

The introduction of the VALUE condition means that the functionality which until now couldonly be effected via the JVA condition is now offered in full via the AVAS interface: it is evenpossible to set values via AVAS, and the SHOW functions enable the user to determinewhich net is setting or testing a particular condition.

Consequently, the functional scope of the JVA condition has essentially been left as inAVAS V1.3; the enhancements of AVAS V2.0 are, in the main, not offered for the JVAcondition; i.e. no condition descriptions are generated for a JVA condition, and it is notpossible to specify an OCCURE-VALUE and ERROR-VALUE. The only one of theenhancements offered for the JVA condition is the timing control for conditions.

Timing control for conditions

It is possible to specify LATEST-OCCURE and OCCURE-DELAY-SOLUTION parametersfor any of the conditions.

LATEST-OCCURE can specify either a relative time (relative to PLAN-START) or anabsolute time. The behavior when this time point is passed is controlled by the specificationof OCCURE-DELAY-SOLUTION.The possible values of OCCURE-DELAY-SOLUTION are START, IGNORE or CANCEL.Specifying these leads to the condition status OCCURRED, IGNORED or ERROR.

This enables a condition to be treated as omitted or errored; in the case of the conditionstatus ERROR, net processing must be resumed by a restart.

To enable a system wait until a prescribed time to be effected at any required point in thenet structure, a new structure element has been introduced with the function “WAIT forTIME”. This enables the user to specify an earliest start point for jobs, or the earliest timeat which a condition is to be tested.

120 U5184-J-Z125-7-76

Preparing for the restart Editing nets

3.5.3 Preparing for the restart

When processing of a net has been abandoned because of an error or a CANCEL-NETstatement with CANCEL-TYPE=SOFT (the net has the status ERROR), the net can berestarted through a RESTART-NET statement. Parameters must be specified in the netdescription for this eventuality. These parameters must take account of the fact that netswith a status of RUNNING can be processed by structure elements that have the statusERROR.

If a structure element in a net has terminated with an error without causing processing ofthe net itself to be abandoned (the net has the status CALLED FOR ERROR), the errorstatus for the net can also be reset by the RESTART-NET statement.

Up to three restart variants can be allocated to each structure element. They define how thenet is to be resumed when the POINT-OF-ERROR for the net occurred in that structureelement.

POINT-OF-ERROR

The POINT-OF-ERROR in the net structure is defined by the element that was allocated astatus of ERROR as the result of an abnormal termination or by the statement CANCEL-NET.In situations where several structure elements have been given a status of ERROR, everysuch element can be selected as the POINT-OF-ERROR via the structure display (maskAVD007).

When it comes to processing a structure element in the POINT-OF-ERROR, one of thethree restart variants specified for that element can be selected.

A restart variant consists of the following parameters:

– RESTART-INDEXIndex in the net at which processing is to be resumed.

– RESTART-NAMEParameter for selecting the structure element of the RESTART-INDEX

– RESTART-TYPEProcessing mode for the structure elements in the RESTART-INDEX

– AUTOMATICType of restart

A restart variant is deemed to be valid if it causes the status of the structure element at thePOINT-OF-ERROR to change to WAITING or SKIPPED and the required changes in statusof the elements are valid. Valid status changes can be specified in the options (see page128).

U5184-J-Z125-7-76 121

Editing nets Preparing for the restart

If an element still has a status of ERROR following a restart, another restart for this elementcan be issued immediately or later.

POINT-OF-RESTART

The POINT-OF-RESTART is defined by that RESTART-INDEX specified for the selectedrestart variant. Processing of the net following a restart resumes with this index, withRESTART-INDEX=END forming an exception. No POINT-OF-RESTART is defined in thiscase.

In cases where the restart index has a number of structure elements assigned to it, theRESTART-NAME parameter can be used to make the required selection. Furthermore,when the restart is initiated by a RESTART-NET statement, individual elements can beexcluded from processing by marking them accordingly in mask ADV005. Which structureelements are to be processed on the subsequent index levels is determined by the netstructure and the synchronization index.The status is not changed if a structure element is excluded from the processing.

If the POINT-OF-RESTART lies within the range of the restart index levels (900 through999), all elements linked via the SYNC-INDEX, up to the first index of normal processing(index 001 through 899), are displayed in the AVD005 mask.From the elements displayed on the first index level of normal processing, those which areto be processed on restart can be selected.No selection is possible if the element in the POINT-OF-ERROR lies within the range of therestart index levels. Making a selection (RESTART-NAME parameter and entering a markin mask AVD005) at the restart index level means that processing of the element in thePOINT-OF-ERROR cannot be prevented.

Restart index

RESTART-INDEX is the name given to an index in the net at which point processing can beresumed. A normal processing index (index 001 through 899) or an index that is onlyprocessed at a restart (index 900 through 999) can be specified as the restart index level.RESTART-INDEX=END is also a valid specification for structure elements in the range ofnormal processing.The specified restart index level must ensure that the ERROR status of the element at thePOINT-OF-ERROR changes to a SKIPPED or WAITING status following the restart. Toensure that the element at the POINT-OF-ERROR is processed, the index level specifiedas the RESTART-INDEX must be associated with the element at the POINT-OF-ERROR.This is done through the synchronization index.

This means that when a restart is performed through index level 9nn, the index for the returnto normal processing (index 001 through 899) must be in the synchronization index of theelement at the POINT-OF-ERROR. If the element at the POINT-OF-ERROR is a restartelement (index levels 900 through 999), the restart index level must address the processing

122 U5184-J-Z125-7-76


sequence that has a RESTART-INDEX greater than index 899. The first index level ofnormal processing with RESTART-NAME=*ALL (net repetition) and the index for the returnto normal processing (RESTART-INDEX and RESTART-NAME from the restart variant 1 ofthe restart element in which the return is defined) is also permitted.

Restart types

The type of restart, and consequently the processing mode for the structure element in thePOINT-OF-RESTART, is defined by the RESTART-TYPE and AUTOMATIC parameters ofthe selected restart variant.

RESTART-TYPE=RESTARTThe structure element or elements in the POINT-OF-RESTART is/are modified by therun control system via the AVAS restart statements #RA, #RI and #RU before the start.

If an SV job is restarted with RESTART-TYPE=RESTART, this means:Before the AVAS agent AVSSINCM is started, the run control system returns thecontents of the server area (positions 129 - 256) of the last run to the task job variable.AVSSINCM recognizes from the contents whether the job has to be restarted (startmode of AVSSINCM) or whether the status of the SV job is to be obtained (QUERYmode of AVSSINCM).

RESTART-TYPE=NORMALThe structure element or elements in the POINT-OF-RESTART is/are brought toexecution without being modified by the AVAS restart statements.

If an SV job is restarted with RESTART-TYPE=NORMAL, this means:AVSSINCM is restarted and branches to start mode. The contents of the job variables(of the last run) are deleted.

A multiple restart at a restart index level means that the mode specified for an elementmay be superseded by another mode. The following procedure has been adopted tocater for this eventuality:RESTART mode overwrites NORMAL mode. By contrast, NORMAL mode does notoverwrite an already defined RESTART mode.

If the restart index level for the sequence linked through the synchronization indexjumps forward (old RESTART-INDEX → new RESTART-INDEX) as the result of a newrestart, the mode of all the relevant elements at the old restart index level will bedeleted.The mode of restart jobs in the range of index levels 900 through 999 can be switchedfrom RESTART mode to NORMAL mode or from NORMAL mode to RESTART modethrough the RESTART-TYPE parameter of restart variant 1.Restart variant 1 must also be used here to define the return to index levels 001 through899. RESTART mode is exited automatically when the first index level of normalprocessing has been completed.

U5184-J-Z125-7-76 123


AUTOMATIC=YESThe restart is normally initiated automatically by the run control system, withoutrequiring entry of the RESTART-NET statement. If a restart is initiated through a restartvariant with AUTOMATIC=YES, AUTOMATIC is reset to NO (only one automatic restartcan be performed through a restart variant).

The user only needs to initiate the restart with RESTART-NET if

– the structure element could not be started due to incorrect ENTER parameters,

– processing of the nets has been interrupted by the run control system with thecommand /INTR tsn,STOP,LEVEL=NAME, or

– processing of the net has been aborted by the CANCEL-NET statement withCANCEL-TYPE=SOFT.

AUTOMATIC=NOThe restart must be initiated through the RESTART-NET statement.

Modifications can be made

– to the net, using MODIFY-SUBMIT-NET and/or

– to structure elements of the net, using MODIFY-SUBMIT-JOB.

The MODIFY-SUBMIT-NET/JOB statements are not selected automatically.

Using the RESTART-NAME parameter to select structure elements on the restartindex level

RESTART-NAME=nameOf the structure elements specified in the index level in the RESTART-INDEX, only thisone will be executed again. Structure elements which had not yet been processed upto this point (WAITING) cannot in this case be excluded. The RESTART-NAMEparameter can only be used to affect the RESTART-TYPE (see also “Status changes inthe POINT-OF-RESTART”, page 125).if a structure element is to be selected using FU=W and TYPE=TIM, the name must bespecified as *DATE. The specified RESTART-NAME must enable the structure elementto be uniquely identified.If the specified element is not in the restart index level, the restart will have to beperformed from the AVD005 mask.

RESTART-NAME=*ALLAll structure elements in the specified index level in the RESTART-INDEX are executedagain.

124 U5184-J-Z125-7-76


RESTART-NAME=*ERRORAll structure elements in the specified index level in the RESTART-INDEX that termi-nated abnormally (STATUS=ERROR) are executed again. The *ERROR parameter isonly processed when the specified index level in the RESTART-INDEX is the same asthe index of the element in the POINT-OF-ERROR.

RESTART-NAME=*NAMEOnly the structure element in the POINT-OF-ERROR is executed again.The *NAME parameter is only processed when the specified index level in theRESTART-INDEX is the same as the index of the element in the POINT-OF-ERROR.

In cases where the restart is taking place at index levels 900 through 999, normalprocessing must be resumed at the index of the POINT-OF-ERROR if RESTART-NAME=*NAME, or if *ERROR is specified in restart variant 1 of the restart element in whichthe return was defined.

The marks in the POINT-OF-RESTART that were set using the RESTART-NAME parameterof the selected restart variants of the element in the POINT-OF-ERROR can be modified bythe operator before initiating the restart (mask AVD005).The marks set cannot be modified if the POINT-OF-ERROR is in the range of restart indexlevels.

Processing of the structure element in the POINT-OF-ERROR must not be prevented by thechoice of restart index level.

The RESTART-NAME parameter is ignored if RESTART-INDEX=END is specified in therestart variant.

Selecting a restart variant

The priority restart variant is selected by specifying the task job variable in the job with theAVAS statement #AVJ#RV=n (see page 70).The restart variant set via the task job variable is entered by the run control system in thestructure element for the job in the POINT-OF-ERROR. The restart is initiated via thisrestart variant unless the user specifies another restart variant via mask AVD012, AVD007or AVD005.If a restart variant is defined neither via the task job variable nor via the structure elementdescription nor by the user via mask AVD012, it will be requested via the parameter field ofmask AVD007 or AVD005.

The restart variant specified via the task job variable or in the structure element is displayedin a special field in mask AVD007 (parameter field R-V).

U5184-J-Z125-7-76 125


Status changes in the POINT-OF-RESTART

If there are two or more structure elements on the index level of the POINT-OF-RESTART,the following general rules apply to the status changes resulting from the RESTART-NETfunction:

M Denotes the mark column. On execution of the RESTART-NET statement,the marks are set internally in accordance with specifications made via theRESTART-NAME in the POINT-OF-ERROR (see CREATE-NET-DESCRIPTION statement).

IND Denotes the index of the POINT-OF-RESTART. The value 080 is selectedhere as an example.

Status before restartDenotes the STATUS displayed with the RESTART-NET statement prior toexecution of the function.

Status after restartDenotes the STATUS set by the RESTART-NET statement after executionof the function.

M IND Status beforerestart

Status afterrestart

Remark

Y 080 ERROR WAITING No status change in branch (WAITING)

080 ERROR ERROR No status change in branch (WAITING)

Y 080 ENDED WAITING All structure elements in the branch are set to WAITING

Y 080 SKIPPED WAITING All structure elements in the branch are set to WAITING

080 SKIPPED SKIPPED No status change in the branch

Y 080 WAITING WAITING No status change in the branch

080 WAITING WAITING No status change in the branch

080 ENDED ENDED No status change in the branch

080 RUNNING RUNNING Job must not be selected

080 NO-OCCURE NO-OCCURE No status change in the branch (WAITING)

080 OCCURRED OCCURRED No status change in the branch

*Y 080 OCCURRED WAITING All structure elements in the branch are set to WAITING

080 EXECUTED EXECUTED No status change in the branch

Y 080 EXECUTED EXECUTED All structure elements in the branch are set to WAITING

Y 080 EXECUTED WAITING Only if FU=M, TYPE=RES is the EXECUTED statusreset to WAITING if RESTART-WAIT-CONDITION =YESis specified (see page 128)

126 U5184-J-Z125-7-76


* Note relating to the condition in OCCURRED statusThe change in status of the condition depends on the optional setting (seepage 128).

A branch is defined by the structure elements linked via the SYNC-INDEX.

Status changes of jobs and conditions

If the status of the structure element in the POINT-OF-ERROR is not modified by theselected restart variant (changed to SKIPPED or WAITING), the restart is rejected with anERROR message or result.The same applies if an element that has a status of RUNNING is specified in the selectedrestart variant.

POINT-OF-RESTART equals POINT-OF-ERRORIn principle, the only structure elements affected by the restart are those linked throughthe SYNC-INDEX to selected elements at the restart index level.All elements with a status not equal to WAITING are given a status of WAITING.If an element with a status of ERROR (but not the element at the POINT-OF-ERROR)has to be given a status of WAITING, the RESTART-WAIT-ERROR system parametercan be used to specify whether a restart is to be permitted or not. The conditions in NO-OCCURE status are not processed; they remain in NO-OCCURE status. Conditionswith a status of OCCURRED are handled by the RESTART-WAIT-CONDITION systemparameter in accordance with the optional settings.

POINT-OF-RESTART precedes POINT-OF-ERRORAll structure elements selected in the POINT-OF-RESTART and all the subsequentelements linked to them via the SYNC-INDEX will be processed.Stand-alone structure elements (those without a predecessor; their INDEX is not usedas a SYNC-INDEX) and their branches will only be processed when their index isstarted by the run control system with the same priority as an index in the SYNC-INDEXsequence that is to be processed.The status of each element is set to WAITING if it is not WAITING already.The conditions in NO-OCCURE status are not processed; they retain the NO-OCCUREstatus. Conditions with the status OCCURRED are handled by the RESTART-WAIT-CONDITION system parameter in accordance with the optional settings.If an element with the status ERROR (but not the element at the POINT-OF-ERROR)has to be given a status of WAITING, the RESTART-WAIT-ERROR system parametercan be used to specify whether a restart is to be permitted or not.

POINT-OF-RESTART follows POINT-OF-ERRORAll that is processed during a restart is the branch of the net between POINT-OF-ERROR and POINT-OF-RESTART (including the structure elements linked to thisbranch through the SYNC-INDEX). All the elements in the branch, including theelement at the POINT-OF-ERROR, are given the status SKIPPED if their status is notENDED or OCCURRED.

U5184-J-Z125-7-76 127


All other branches of the net with SYNC-INDEX=RESTART-INDEX are not affected bythe restart, and the structure elements retain their current status (they are not given thestatus SKIPPED).If a job with the status ERROR (but not the element at the POINT-OF-ERROR) has tobe given the status SKIPPED, the RESTART-SKIP-ERROR system parameter can beused to specify whether a restart is to be permitted or not.If a condition with the status NO-OCCURE has to be given the status SKIPPED, theRESTART-SKIP-CONDITION system parameter can be used to specify whether arestart is to be permitted or not.

RESTART-INDEX is in the range of restart jobsThe restart jobs of the selected processing sequence on the index levels 900 through999 are given the status WAITING.The return index (RESTART-INDEX restart variant 1) is interpreted as a RESTART-INDEX (Index level 001 through 899).How the net structure is processed (change in status) depends on the relationshipbetween the return index to the index job at the POINT-OF-ERROR.

RESTART-INDEX=ENDIn all branches of the job at the POINT-OF-ERROR, the jobs with a status that is notENDED and the conditions with a status that is not OCCURRED are given the statusSKIPPED. The branches are processed as far as their end condition (SYNC-INDEX=END).If the job at the POINT-OF-ERROR itself has SYNC-INDEX=END, only one job will begiven the status SKIPPED. If a job with a status of ERROR (but not the job at the POINT-OF-ERROR) has to be given the status SKIPPED, the RESTART-SKIP-ERROR systemparameter can be used to specify whether a restart is to be permitted or not. If acondition with a status of NO-OCCURE has to be given the status SKIPPED, theRESTART-SKIP-CONDITION system parameter can be used to specify whether arestart is to be permitted or not.

128 U5184-J-Z125-7-76


Optional settings

Certain default values in accordance with the requirements of the computer center can bedefined for restart processing. These settings are defined via the system parameters andare applicable throughout the system. The AVAS administrator can thus determine whetheror not the RESTART-NET operation is to be used to effect the required change in status.

The default values RESTART-SKIP-ERROR and RESTART-SKIP-CONDITION describehow the RESTART-NET operation responds when the choice of restart variant means thata part of the net is not to be executed.

RESTART-SKIP-ERROR={YES|NO}

=YES Structure elements with a status of ERROR can be allocated a status ofSKIPPED.

=NO The restart will be rejected if a structure element status has to be changedfrom ERROR to SKIPPED.The only exception to this is the structure element at the POINT-OF-ERROR.

RESTART-SKIP-CONDITION={YES|NO}

=YES Conditions with a status of NO-OCCURE or WAITING can be allocated thestatus SKIPPED.

=NO The restart will be rejected if a condition status has to be changed from NO-OCCURE or WAITING to SKIPPED

The default values RESTART-WAIT-ERROR and RESTART-WAIT-CONDITION describehow the RESTART-NET operation responds when the choice of restart variant means thata part of the net is to be executed again.

RESTART-WAIT-ERROR={YES|NO}

=YES Structure elements with a status of ERROR can be allocated the statusWAITING.

=NO The restart will be rejected if a structure element status has to be changedfrom ERROR to WAITING.The only exception to this is the structure element at the POINT-OF-ERROR.

RESTART-WAIT-CONDITION={YES|NO}

=YES Conditions with a status of OCCURRED are to be changed to the statusWAITING. They are retested following the restart to see whether thecondition is satisfied.

U5184-J-Z125-7-76 129


Structure elements with FU=M, TYPE=RES and the EXECUTED status arealso set to the WAITING status because FU=C, TYPE=RES reserves aresource and FU=M, TYPE=RES releases it again.

Structure elements with FU=D and FU=A, TYPE=RES are not changedfrom EXECUTED to WAITING.

After processing of a structure element with FU=D, TYPE=RES, theresource can no longer be addressed after a restart.

=NO Conditions with the status OCCURRED are not processed during therestart. They retain their OCCURRED status and are not checked followingthe restart.

Note that resources are no longer reserved after processing with FU=M,TYPE=RES.The resource may have to be reserved again via an index of the restartprocessing with FU=C, TYPE=RES.

Conditions whose status has changed from NO-OCCURE to SKIPPED as a result of theRESTART-NET statement are deemed to be satisfied and are treated by RESTART-NET asconditions with the status OCCURRED.

All status changes (JOB-STATUS, COND-STATUS and NET-STATUS) are logged in the netjournal.If the user performs several partial restarts (AVD007 mask; several structure elements witha status of ERROR processed), a journal record is output for each one.If the net cannot be restarted because of an error (ERROR result displayed in the AVD012mask, an error message is sent to the net journal.

130 U5184-J-Z125-7-76

CREATE-NET-DESCRIPTION Statements for net editing

3.5.4 Statements for net editing


CREATE-NET-DESCRIPTIONCreate net description

All the parameters in the description of a net, and of the associated structure elements, canbe defined using the CREATE-NET-DESCRIPTION statement and created in the net libraryNETLIB.

Depending on the OBJECT operand, appropriate masks are selected for entering the data.If the OBJECT operand is omitted, first the AVN001 mask for net parameter input ispresented, followed by the AVN020 mask for entering the net plan data, then the AVN006mask for entering the net mask table and finally by the AVN004 mask for entering the netstructure. Switching from mask AVN001 to AVN020, AVN006 and AVN004 is alwayseffected by means of the CONTINUE operation.

Switching masks in the reverse direction only becomes possible after the operand value forOBJECT has been changed.

Structure elements which do not yet have a complete set of parameters are logged usingCHECK, as are further errors (see the description of the CHECK function in “AVAS for theAdministrator“ [3]). CHECK can be directly called in the CMD input field in masks AVN001,AVN004, AVN006 and AVN020, and is automatically called when a SAVE is executed.Depending on the message, the network will not be saved, or will be saved as non-executable or executable.

In the AVN004 mask, the net structure descriptions can be marked with S if the corre-sponding parameters are to be supplied.Depending on the values of the FU and TYPE parameters, the NEXT parameter can beused to select parameter masks (NEXT=DES) or plan data masks (NEXT=SYM). After anEXECUTE, the appropriate masks are presented.

CREATE-NET-DESCRIPTION Set up a net description

MODIFY-NET-DESCRIPTION Modify a net description

CHANGE-NET-DESCRIPTION Large-scale change to nets

COPY-NET-DESCRIPTION Copy a net description

SHOW-NET-DESCRIPTION Display a net description

DELETE-NET-DESCRIPTION Delete a net description

U5184-J-Z125-7-76 131

Statements for net editing CREATE-NET-DESCRIPTION

The following parameters in the AVN001 mask are given valid default values:

NET-DOC=*NONENET-TYPE=1RUN-CONTROL-SYSTEM=*STDUSER-PAR-FILE=*NONE

The following parameters in the AVN020 mask are provided with valid default values evenif the mask is not called up:

SELECT-TURNUS=1

and the first mandatory PLAN-START line:

PLAN-START DATE / SYMDAT=*NONELATEST-START=*NONEDELAY-SOLUTION=WAITLIFE-TIME=*STD

The following structure element parameters, which are specified using mask AVN004, aresupplied with valid default values even if the continuation masks are not called up:

FUNCTION=C , TYPE=JVA:

JVA-POSITION=001JVA-LENGTH=001COND-VALUE= ´ ĆOND-JVA-NAME=NAME - name of the structure element

FUNCTION=C, TYPE=NET:

CREATED-BY=NAME - name of the structure element

FUNCTION=J / P , TYPE=EXT:

ENTER-FILE=NAME - name of the structure element with no user group

FUNCTION=X , TYPE=MOD/STD/EXT:

SERVER-NAME=*STD

FUNCTION=X , TYPE=EXT:

FILENAME=NAME - name of the structure element with no user group

FUNCTION=P , TYPE=EXX:

ENTER-FILE=NAME - name of the structure element with no user group

132 U5184-J-Z125-7-76

CREATE-NET-DESCRIPTION Statements for net editing

The following apply for any of the masks selected via AVN004:– CONTINUE saves the entries– IGNORE ignores the entries– the next marked record for mask AVN004 is presented, or mask AVN004 is re-

presented.

SAVE is used to store the net description from any of the masks AVN001, AVN020, AVN006or AVN004.

If a net description is stored by means of SAVE, it can only be modified using MODIFY-NET-DESCRIPTION or CHANGE-NET-DESCRIPTION.

NET-NAME=[$ug_]netnameName of the net under which the net description is to be entered as an element in the netlibrary.

The user group need not be specified. The user group of the person carrying out thefunction is added internally to the net name by AVAS.Even privileged users are only allowed to create nets for their own user groups.

OBJECT=Selects the mask for entering net description data. If OBJECT is not specified, maskAVN001 is displayed.

OBJECT=NETThe AVN001 mask for net parameter input is presented.

OBJECT=PSTThe AVN020 mask for entering the net plan data is presented.

OBJECT=MAPThe AVN006 mask for entering the net mask table is presented.

OBJECT=STRThe AVN004 mask for entering the structure elements is presented.

CREATE-NET-DESCRIPTION

NET-NAME=[$ug_ ]netname

[OBJECT=NET | PST | MAP | STR]

U5184-J-Z125-7-76 133

CREATE-NET-DESCRIPTION Mask AVN001

AVN001 - Display net parameters for input

Mask AVN001 is used to specify the general parameters the net.

The parameter fields NET-DOC, NET-TYPE, RUN-CONTROL-SYSTEM and USER-PAR-FILE are preset to default values. However, these values can be replaced by current values.

The parameters NET-ACCOUNT, NET-CAT, NET-CLASS, NET-LOG, NET-PARAMETER,NET-PASSWORD and NET-USER can be used to specify ENTER parameters globally forthe tasks in the net. They are employed whenever AVAS has no presettings for the ENTERcall in the corresponding parameters of a job structure description and the parameterENTER-PARAMS=NET is set in mask AVN002 or AVN009.

In the case of S procedures with TYPE=EXX, the value of NET-PARAMETER is not takeninto account. Parameters for the external procedure can only be defined via JOB-PARAMETER.

If no ENTER parameters have been set in the net or job description, they are taken fromthe /SET-LOGON-PARAMETERS or /LOGON command of the job in the case of /ENTER-JOB (see the appropriate volume of the "Commands" [7] manual) if ENTER-PARAMS=LOGON is specified.In the case of S procedures (FU=P) and SV jobs (FU=X), ENTER-PARAMS=NET must bespecified.

All BS2000 parameters for the ENTER call must be entered in the manner expected byBS2000 (e.g. passwords enclosed in single quotes or as C’value’).

NET-ACCOUNT Input parameter(BS2000 ENTER parameter).

Account number under which all jobs in the net are billed. It is usedas the default value for the JOB-ACCOUNT parameter of all jobs inthe net (see the AVN002 mask, JOB-ACCOUNT parameter).

NET-CAT Input parameter(BS2000 ENTER parameter).Parameter for job distribution within an MSCF network (MultiSystem Control Facility); see "AVAS for the Administrator" [3].The catalog ID of the processor on which the batch task is to runmust be specified. The target processor is addressed by directly orindirectly specifying a catalog ID.If *ANY is specified as the catalog ID, the processor on which AVASis started must belong to an XCS network (see the chapter dealingwith multiprocessor operation with AVAS in “AVAS for the Adminis-trator“ [3]).{’catid’ | *ANY | jvname}

134 U5184-J-Z125-7-76

Mask AVN001 CREATE-NET-DESCRIPTION

NET-CLASS Input parameter(BS2000 ENTER parameter).

Job class in which all jobs in the net are classified. It is used as thedefault value for the JOB-CLASS parameter of all jobs in the net(see the AVN002 mask, JOB-CLASS parameter).

NET-DOC Input/output parameter.{*STD | element | *NONE}

*STD The documentation is sought or stored under the standard name$ugnet_netname in the DOCLIB.

element Element name for the documentation of the net in the DOCLIB orDOCSYS.$ug_docname$ugsys_docnamedocname

The maximum length of docname is 37 characters. If no user groupis specified, the documentation is sought in the DOCLIB under theuser group of the net. If $ugsys is specified, the documentation issought in the DOCSYS.Only those elements for which the user group of the documentationelement is the same as the user group of the net can be edited usingthe DOCUMENT operation. Elements from other user groups canbe read but not written back. The entry of NEW-DOCUMENT-NAMEis expected via the AVS016 mask.

*NONE No documentation is used.

If the DOCUMENT operation is entered for the net, the followingmessage is output:AVS4090 THE DOCUMENT-FUNCTION IS NOT AVAILABLE

NET-LOG Input parameter(BS2000 ENTER parameter).

Indicates whether (YES) or not (NO) the SYSOUT log of jobs in thenet is to be printed out.The value specified here is used as the default value for the LOGparameter of all jobs in the net (see the AVN002 mask, LOGparameter).

NET-NAME Output parameter.Name of the net to be created. The user group is prefixed to the netname, even if it is not specified in the operand.

U5184-J-Z125-7-76 135


NET-PARAMETER Input parameter(BS2000 ENTER parameter).

Specifies additional attributes for the selected job class in theENTER call. The entry is regarded as the default value for the JOB-PARAMETER parameter of all tasks in the net (see mask AVN002/AVN009, JOB-PARAMETER).If parameters which cannot be defined directly are to be specifiedfor the BS2000 ENTER call, they have to be entered in the form,NAME1=value1,NAME2=value2,...The parameters are then passed upon the ENTER call but notvalidated by AVAS.

Note

In the case of structure elements with FUNCTION=P andTYPE=EXX, the value of NET-PARAMETER is not taken intoaccount.Parameters for the external task can only be defined via JOB-PARAMETER.

NET-PASSWORD Input parameter(BS2000 ENTER parameter).LOGON password.

C´........´1 - 8 alphanumeric characters.

X´........´1 - 16 hexadecimal characters.

This is used as the default value for the PASSWORD parameter ofall jobs in the net (see the AVN002/AVN009 mask, PASSWORDparameter).

The NET-PASSWORD field is blanked out in the AVN001 mask. Thepassword is not displayed.

NET-TEXT Input parameter.Brief description of the net, up to 120 characters long. If a text isspecified, it is displayed in all net creation masks.

NET-TYPE Input/output parameter.Specifies whether nets with the same name but different start timesare to be started.{1 | 2 | 3}

1 The net is started regardless of whether a net with the same nameis or was running.

136 U5184-J-Z125-7-76


2 The net is not started as long as a net with the same name isrunning. A net is deemed to be running if it has the status ERROR,CONDWAIT or HOLD following RUNNING (at least one job of thenet has been started or a condition has been checked). If two ormore nets with the same name and not of type 1 are waiting to start,the net with the earliest PLAN-START time will be started first.

3 The net will only be started if no net with the same name has beenbrought to execution since the last time the run control file wasreorganized (see "AVAS for the Administrator" [3]).

The restrictions specified by NET-TYPE=2 or 3 apply only to thosenets which are brought to execution within one RUN-CONTROL-SYSTEM.

NET-USER Input parameter(BS2000 ENTER parameter).

User identification under which all jobs in the net are to run (with SVjobs the BS2000 user ID under which AVSSINCM is to run).It is used as the default value for the USER parameter of all jobs inthe net (see the AVN002 mask, USER parameter).

RUN-CONTROL-SYSTEMInput/output parameter.{avak | *STD}

avak Name of the run control system (German abbreviation) that is tocontrol net processing.

Note

A run control system other than the one defined for the user groupin the system parameters can only be specified if the user has theappropriate authorization.

*STD By default, this is assigned the name of the run control systemdefined for the user group in the system parameters.

U5184-J-Z125-7-76 137


USER-PAR-FILE Input/output parameterFile containing parameters for the modification.{*NONE | *STD | filename | libname(element[,type])}

*NONE No USER-PARAM-FILE is used or the name of the file is specifiedvia the AVM012 mask in the case of CREATE-PROD-NET.

*STD The name of the USER-PARAM-FILE is sought withPARAM.$ug.netname[.yymmdd[.hhmmss]] and descending classi-fication in the case of CREATE-PROD-NET.

filename The parameters contained in this file are used during the modifi-cation process.

libname(element[,type])The parameters are sought in the specified element of the definedlibrary.If the type is not specified, the element is expected as type S.Valid entries for type are S, J, P and D.

Note

*STD is output as the default value unless *NONE is defined as thedefault value via the system parameters (only in the case ofCREATE-NET-DESCRIPTION). With MODIFY-NET-DESCRIPTION, the value saved by the user under CREATE-NET-DESCRIPTION applies.

If CONTINUE is entered in the AVN001 mask, the AVN020 mask will be displayed to permitthe net plan data to be entered.If net masks (mask AVN006) or structure elements (mask AVN004) are to be definedimmediately, OBJECT=MAP or OBJECT=STR respectively must be entered in the operandfield.

138 U5184-J-Z125-7-76


AVN020 - Display the net plan data to be entered

Mask AVN020 allows start dates/times to be defined, deleted or modified.

PLAN-START is processed when the CREATE-PLAN-NET statement is processed.

The first record is created with the start date/time *NONE, even if the mask is not called up.This record will be used if the calendar is not used to plan the net. It cannot be deleted.Only the parameters DELAY-SOLUTION, LATEST-START and LIFE-TIME can be modified.

So that the net can later be planned by using the calendar to specify a period, at least onemore start date/time should be entered.

If a number of start times are specified in the PLAN-START parameter, a value must bespecified in TIME corresponding to each value in SYMDAT/DATE.

A maximum of 130 start dates/times are permitted for use in planning with the calendar.

The parameters LATEST-START, LIFE-TIME and DELAY-SOLUTION are permitted foreach start date/time.

DELAY-SOLUTIONInput/output parameter.Action to be taken in case of an untimely net start (LATEST-STARThas expired).{WAIT | START | IGNORE | CANCEL}

If nothing is specified, the value defined for DEFAULT-NET-DELAYvia the generation parameters is used.

WAIT The net should continue to wait.

START The net should be started.

IGNORE The net is not started. If other nets or jobs are dependent on this net,these dependencies are regarded as resolved if their OCCURE-VALUE is used to test for the IGNORED status.

CANCEL The net is not started and is regarded as having terminated abnor-mally.

This parameter takes effect when

– nets are released after LATEST-START has expired (SUBMIT-NET)

– nets are in the HOLD state during the interval betweenEARLIEST-START and LATEST-START

– the run control system is inactive during the interval betweenEARLIEST-START and LATEST-START

U5184-J-Z125-7-76 139


– two or more nets of the same name are released with NET-TYPE=2 or 3, but they cannot be started in the interval betweenPLAN-START and LATEST-START.

Once LATEST-START has expired, the net status is dependent onthe DELAY-SOLUTION parameter:

LATEST-START Input/output parameter.Latest point in time, relative to the planned start time in the net name(PLAN-START), at which the net can be started.{nnn.hh.mm | *nn.hh.mm | *NONE}

nnn.hh.mm Date and time span relative to PLAN-STARTnnn is the number of calendar days, in the range 000 to 999.

*nn.hh.mm Relative date span and absolute time relative to PLAN-START.nn is the number of calendar days, in the range 00 to 99

*NONE The net can be started with any required delay.

If no entry is made, *NONE is assumed. The value used for *NONEis the value specified for DEFAULT-LATEST-NET-START via theparameter generation.

LIFE-TIME Input/output parameter.Lifetime of the ’end-of-net’ event for this net. When the run controlfile is reorganized, the event entry is not deleted until this time spanhas elapsed. If the time has elapsed and the event entry has still notbeen deleted, any subsequent test will be unable to find it.The life time is relative to the value of PLAN-START.{nnn.hh.mm | *STD | *NONE}

nnn.hh.mm When the net is released by SUBMIT-NET and REPEAT-NET, acondition description for the net is recorded in the run control file.The time span is relative to PLAN-START, and is equal to nnncalendar days, hh hours and mm minutes.

*STD Default value for LIFE-TIME defined in the system parameters(DEFAULT-LIFE-TIME).When the net is released by SUBMIT-NET and REPEAT-NET, acondition description for the net is recorded in the run control file.

DELAY-SOLUTION NET-STATUS

WAITSTARTIGNORECANCEL

WAITINGRUNNING or CONDITION-WAITIGNOREDABENDED

140 U5184-J-Z125-7-76


*NONE When the net is released by SUBMIT-NET and REPEAT-NET, nocondition description for the net is recorded in the run control file.

M Input parameterMark column, for selecting the start date/time to be edited.

D (Delete) The marked record is to be deleted.

Y (Yes) The values displayed in the mask can be modified.

N (No) All unmarked records can be modified.

If no marks are entered, then after EXECUTE the data for any of thedisplayed records can be modified.

Note

When the D, Y and N marks are used, the work window cannot berepositioned.If the EXECUTE operation is entered together with a + or - mark,the records in the repositioned work window are presented formodification.

NET-NAME Output parameterName of the net. This net name is prefixed by the user group, evenif the latter was not specified in the operand.

NET-TEXT Output parameterBrief description of the net, which may be a maximum of 120characters long. This text is displayed in all the net creation masks.

PLAN-START Input/output parameterStart time/date for the net. PLAN-START is defined by either of thetwo parameters DATE/SYMDAT, with which a date is specified,together with TIME for specifying the time of day.

DATE/SYMDAT {[*dd.mm.yy] | [symdat [±n]}The date may be specified either in real form (by DATE) or symbolicform (by SYMDAT).

*dd.mm.yy A real date is specified with a leading asterisk (*). The net isprovided for planning on those days which are explicitly specified. Itcan be planned either by specifying a period or by specifying the netname.

If two or more start times are specified in the PLAN-STARTparameter, a corresponding value must be specified in LATEST-START for each value in PLAN-START. A maximum of 130 symbolicor real start dates/times are permitted.

U5184-J-Z125-7-76 141


PLAN-START is processed within the framework of the CREATE-PLAN-NET statement.

symdat ±n Execution of CR-PLAN-NET replaces the symbolic date with realdates if the calendar is being used for planning the net (PERIODspecified).

The symbolic date can also be specified in the form symdat[±n].This results in planning of the net n days before or after the datedefined by SYMDAT in the calendar. Calendar days on which noproduction takes place are not included in the count.For ±n, values between 1 and 99 are permissible.In this case the maximum length of the symdat name is 17 or 18characters.

*NONE Output parameter(see the general description of mask AVN020).

TIME hh:mm:ssTime of day at which the net is to be started.AVAS ignores any seconds specification.

SELECT-TURNUS Input/output parameter.Characteristic for forming net run variants.{1 | 2 | .. 9}

If this value matches the value for SELECT-TURNUS in thestructure element, the structure element is planned for processingin CREATE-PLAN-NET.

If CONTINUE is entered in mask AVN020, mask AVN006 will be displayed; in this areentered the net masks required to modify execution of the net.If structure elements (mask AVN004) are to be defined immediately, OBJECT=STR mustbe entered in the operand field.

142 U5184-J-Z125-7-76


AVN006 - Table of net masks for entering net parameters

FORMAT-NAME Input parameter.Name of a net mask, up to 8 characters long.This user mask is to be presented with the COLLECT-NET-PARAMSstatement in order to define run parameters that are validthroughout the net.

A maximum of 32 net masks are permitted for each net.

FORMAT-TEXT Input parameter.Remarks describing the net mask in greater detail. The text may beup to 40 characters long.

M Input parameter.Mark column.If net masks and the texts assigned to them are to be deleted, theymust be marked with D.

D (Delete) The marked mask is to be deleted from the table of net masks.

Y (Yes) The values displayed via the AVN006 mask can be modified.

N (No) All unmarked net masks can be modified.

If there are no marks, following EXECUTE the data in all displayednet masks can be modified.

Note

In connection with the D, Y and N marks, the work window cannotbe repositioned.If the EXECUTE operation is entered together with a + or - mark, thenet masks of the repositioned work window are presented formodification.

Entering CONTINUE causes the AVN004 mask to be displayed.

Entering OBJECT=STR/NET in the operand field enables a branch to be made to maskAVN004 or AVN001.

U5184-J-Z125-7-76 143


AVN004 - Display the net structure for entering structure elements

The AVN004 mask can be used to define, delete or modify structure elements. A maximumof 256 structure elements may be defined.

Defining:

The following parameters are the minimum which must be specified to define a structureelement:

In mask AVN004, the net structure records can be marked with S if the correspondingparameters are to be supplied. Depending on the values of the FU and TYPE parameters,the NEXT parameter can be used to select parameter masks ((NEXT=DES) or plan datamasks ((NEXT=SYM). After an EXECUTE, the appropriate masks are presented.

IND Index of the structure element itself

FU Function of the structure element

TYPE Type of the structure element:- FU is C: standard NET- FU is J, P or X: standard MOD

NAME Name of the structure element

for NEXT=DES

FU TYPE Mask

J STD/MOD/EXT AVN002

P STD/MOD/EXT/EXX AVN002

X STD/MOD/EXT AVN009

C JVA AVN003

C NET/JOB/RES/VAL AVN008

A/M/D RES/VAL AVN030

D NET/JOB AVN031

W TIM AVN032

for NEXT=SYM

J / X STD/MOD/EXT AVN021

P STD/MOD/EXT/EXX AVN021

C JVA AVN022

C NET/JOB/RES/VAL AVN022

A/M/D RES/VAL AVN024

D NET/JOB AVN024

W TIM AVN023

144 U5184-J-Z125-7-76


The following apply for any of the masks selected via AVN004:

– CONTINUE saves the entries– IGNORE ignores the entries– the next marked record for mask AVN004 is presented, or mask AVN004 is re-

presented.

Note

An entry for a condition is created in the run control file

– by a net structure element using the ADD function, if the index level is processed bythe run control system (only for COND-TYPE=VALUE and =RESOURCE)

– by the release of a net, if a LIFE-TIME parameter (other than *NONE) is specifiedfor the net (only for COND-TYPE=NET)

– by the release of a net, if a LIFE-TIME parameter (other than *NONE) is specifiedfor a job (only for COND-TYPE=JOB)

The ERROR status will be set in the following cases:

Even for elements with the named functions, three restart variants may be defined.

The assignment of a condition test (FU=C) to a condition description takes place atexecution time:

– in the case of RESOURCE and VALUE conditions via the unique name of the condition

– in the case of NET and JOB conditions, via the (condition) description which has thesmallest time difference (relative to PLAN-START) from the planned start of the netperforming the test.

If, when a condition description with the function FU=C is tested, no entry of the right typeis found with the specified name, the status will be set to MISSING.

A =ADD Creation of a condition description of type RESOURCE, VALUE

If a condition description with the specified name already exists.

M =MODIFY Modification of a condition description

If the condition description does not exist, or if a resource is to be released but it isnot in use.

D =DELETE Deletion of a condition description

If there is no condition description with the specified name, or if a resource is in use.

W =WAIT Wait for a time

For a CANCEL-NET statement with CANCEL-TYPE=SOFT

U5184-J-Z125-7-76 145


For conditions which test the status of a condition description (NET, JOB, RES), the statusMISSING is permitted as a testable status.

All the conditions are retested in the next cycle of the run control system.

If structure elements are to be inserted in or appended to the net structure which is to becreated, their parameter values must be entered in a blank line in mask AVN004. The newline will be placed in the net structure at a position corresponding to its index.

Modifying:

After any defined structure element has been marked with a Y, its individual parametervalues can be modified by overwriting them.

Note

For defined structure elements, modifying the function, FU, results in the deletion of allthe assigned parameter values. New default values will be assigned, depending on thefunction and type.

Exception

When a change is made from J to P or vice versa, the defined parameter values areretained.

Deleting:

By marking them with a D, structure elements can be deleted.

FU Input/output parameterThe function of the structure element

A (Add) This element of the net description is a structure element whichcreates a condition description.

C (Compare) This element of the net description is a condition description whichwaits until a condition is satisfied.

D (Delete) This element of the net description is a structure element whichdeletes a condition description.

J (Job) This element of the net description is a structure element whichexecutes jobs.

M (Modify) This element of the net description is a structure element whichmodifies a condition description.

P (Procedure) This element of the net description is a structure element whichexecutes procedures.

146 U5184-J-Z125-7-76


W (Wait) This element of the net description is a structure element whichcauses a timed wait.

X (SV job) This element of the net description is a structure element whichexecutes SV jobs.

IND Input/output parameter3-digit index (001, ..., 999) of the structure element. This is either aJOB-INDEX or a COND-INDEX, depending on how the FU param-eters are defined.New structure elements are defined in a blank line in the mask.

When the index is modified, the element is inserted at the positionin the net structure corresponding to the new index. If there isalready a defined element at the specified index level, the modifiedstructure element will be positioned after the existing one.

M Input parameterMark column, for selecting structure elements.

S (Select) Selects the structure element which is to be defined by furtherparameters, or the parameters of which are to be modified.Depending on the parameters FU, TYPE and NEXT, the appropriatecontinuation mask is output after EXECUTE.

D (Delete) The marked structure element is deleted from the net description.

Y (Yes) The values of the structure element which are displayed in maskAVN004 can be modified.

N (No) All unmarked structure elements can be modified.

If there are no marks, then the data for all the displayed structureelements can be modified after EXECUTE is entered.

Note

In connection with the D, Y and N marks, the work window cannotbe repositioned.If the EXECUTE operation is entered together with a + or - mark,the structure elements in the repositioned work window arepresented for modification.

NAME Input/output parameterName of the structure element. This depends on the FU and TYPEparameters.

Within each AVAS system, the name of each condition descriptionmust be unique across all the types of condition.The JVA condition is excepted from this.

U5184-J-Z125-7-76 147


For FU=J/P/X, the user group for the net, or the system user group, may bespecified.The specified user group is only used here in addressing the LIB forthe CREATE-PROD-NET (JCLLIB/JCLSYS) and SUBMIT-NET(JMDLIB/JMDSYS) statements.If a USER-PARAM-FILE is to be assigned to the task (AVN002 orAVN009 mask), the name of the structure element can be up to 20characters long (without the user group).If LIFE-TIMEî*NONE, a condition description is always created withthe user group of the net.

If the functions FU=J, FU=P and FU=X are used with the samename in a net, this will be identified and logged by the CHECKfunction as an error.The net cannot be planned.

For FU=A/D, only the user group for the net may be specified.

For FU=C and TYPE=NET/JOB/RES/VAL

and FU=M with TYPE=RES/VAL, it is also possible to specify a foreign usergroup.If a NET or JOB condition refers to another user group (i.e. not theuser group of the net), this foreign user group must be specified. Ifno user group is specified, the user group of the net is assumed.When the name is specified in abbreviated form, the condition testis assigned to the description for which the PLAN-START is beforethe PLAN-START of the net making the reference by the smallesttime.

For FU=W either *DATE or a name may be specified.

For FU=C with TYPE=JVA, the name of the job variableThe name of the job variable can be modified in the COND-JVA-NAME parameter of mask AVN003.

*NONE is no longer copied into the name of the structure element.

In a NET condition, *NONE is no longer permitted as the name ofthe structure element, and may only be specified under theCREATED-BY NET-NAME parameter.The condition is always satisfied if all possible status values arespecified under OCCURE-VALUE, or under ERROR-VALUE with arestart in the SYNC-INDEX.

NET-NAME Output parameterName of the net

148 U5184-J-Z125-7-76


NET-TEXT Output parameterBrief description of the net

NEXT Input/output parameter{DES | SYM}Controls the presentation of masks for structure elements markedwith an S.

DES (DESCRIPTION)The appropriate mask for entry of the parameters is presented.

SYM (SYMDAT)The appropriate mask for entry of the plan data is presented.

Depending on the values of the FU and TYPE parameters, thecontinuation masks will then be presented after EXECUTE (seepage 143).

RESTART-IND

V1 V2 V3 Input/output parameter{index | END}The restart index can be defined for the three possible restartvariants. Without this index, no restart variant is possible.

index The index level to be used for any restart (of the net).A restart is permissible in all index ranges (001 - 999) for allstructure elements, irrespective of their function and type.

END In the event of a restart (of the net), there should be no furtherprocessing of the structure element and its dependents.It is not permissible to specify END for restart jobs (index 900 - 999).The SYNC-INDEX of this element or a successor must be synchro-nized to END, or else the CHECK operation will output a warning.

SYNC-INDEX Input/output parameter.Index level at which the job or condition is to be synchronized.{index | NXT | END }

index The value of SYNC-INDEX must be greater than the value definedfor IND. It is not permitted to specify the index level of a restart job.The system waits at this index level for the job to terminate or for thecondition to be met.

NXT Synchronization takes place at the next higher index level.

END Normal job termination or the satisfaction of the condition is theprerequisite for normal termination of the net, i.e. net terminationforms the basis for synchronization.

U5184-J-Z125-7-76 149


Note

Only NXT is permissible for the restart index levels (index > 899).For the restart index levels, SYNC-INDEX is replaced by the indexspecified for restart variant 1.

TYPE Input/output parameterType of the structure elements

{MOD | STD | EXT | EXX | JVA | NET | JOB | RES | VAL | TIM}

Depending on the function FU, the following are possible entries:

MOD The job, S procedure or SV job is saved in the AVAS system and issubject to net modification. It must be created as a temporaryproduction task by a CREATE-PROD-NET statement.

Note

If a structure element with TYPE=MOD is used more than once in anet (same name), either the same user group (user group of the netor system user group) or no user group must always be specified.If a USER-PARAM-FILE is to be assigned to the task (AVN002 orAVN009 mask), the name of the structure element can be up to 20characters long (without the user group).Any violation of this rule will be identified and logged by the CHECKfunction as an error.The net cannot be planned.

STD The job, S procedure or SV job is saved in the AVAS system and isnot subject to net modification. It must be created by a CREATE-PROD-JOB statement.

FU TYPE

J/P/X MOD

J/P/X STD

J/P/X EXT

P EXX

C JVA

C/D NET

C/D JOB

C/A/M/D RES

C/A/M/D VAL

W TIM

150 U5184-J-Z125-7-76


EXT The job, S procedure or SV job is not saved in the AVAS system. Itis assigned using the file name specified under ENTER-FILE orFILENAME (see mask AVN002 or AVN009).

EXX The S procedure is not saved in the AVAS system. It is assignedusing the file name specified under ENTER-FILE. The S procedurerun is monitored via an external job variable.

JVA For FU=C, net processing waits for a condition to be satisfied by adefined value in a job variable.

NET For FU=C, net processing waits for a condition in another net to besatisfied. The LIFE-TIME parameter determines how long thecondition description remains available for testing.For FU=D, the condition description for a predefined net is deleted.

JOB For FU=C, net processing waits for a condition on a job to besatisfied. The LIFE-TIME parameter determines how long thecondition description remains available for testing.For FU=D, the condition description for a prescribed job is deleted.

RES For FU=C, net processing waits for a condition on a resource to besatisfied.The status of the resource is modified by the satisfaction of thecondition.For FU=A, a condition description for a resource is created.For FU=M, a condition description for a resource is modified.For FU=D, a condition description for a resource is deleted.

VAL For FU=C, net processing waits for a condition to be satisfied by adefined value.For FU=A, a condition description with a defined value is created.For FU=M, a condition description with a defined value is modified.For FU=D, a condition description with a defined value is deleted.

TIM Net processing is subject to a timed wait. The time interval isspecified by OCCURE-DATE SYMDAT in mask AVN023.

RESULT Output parameter.Confirmation of the action performed.

UPDATED The marked structure element has been modified. (Return to maskAVN004 by a CONTINUE operation).

INSERTED The defined structure element has been inserted.

U5184-J-Z125-7-76 151


MOVED The structure element whose index (IND) was modified has beenmoved.

NO-UPDATE The marked structure element has not been changed. (Return tomask AVN004 by an IGNORE operation).

AVN002 - Display and input parameters for structure elementswith FU=J/P and TYPE=STD/MOD/EXT/EXX

In this mask, the structure elements for executing jobs and S procedures (tasks) arespecified.

The mask is displayed in various formats, depending on the type of structure elementdefined:If TYPE=EXT/EXX, the input fields ENTER-FILE and FILE-PASSWORD are displayed; ifTYPE=MOD, the USER-PAR-FILE input field is displayed.

Otherwise, the structure of the mask is identical in all formats.

ENTER-FILE Input/output parameter.Name of the file which is to be executed in the case of TYPE=EXT/EXX. The default value is the name from the structure, without"ug_".

ENTER-PARAMS Input/output parameter.Source of the parameters for the ENTER call used to start this task.{NET | LOGON}

NET The ENTER parameters are taken from the net description, withspecifications for the task being given precedence over specifica-tions for the net.

LOGON The ENTER parameters are taken from the LOGON statement ofthe task. The data in the LOGON statement is accepted by the runcontrol system without validation. The catalog ID from the netdescription is not evaluated.The LOGON entry is not permissible if JOB-TYPE=EXT and/or a jobdescription record for S procedures is processed.

FILE-PASSWORD Input parameterPassword of the file specified under ENTER-FILE (only forTYPE=EXT/EXX).{*NONE | password}

*NONE The ENTER call is issued without a password.File password:

C´....´: 1 - 4 alphanumeric characters.X´....´: 1 - 8 hexadecimal characters.

152 U5184-J-Z125-7-76


Entry of a decimal number is permitted: positive or negative valuewith a maximum of 10 digits.

The FILE-PASSWORD field is blanked out in the mask.

In the case of ENTER-PROCEDURE (FU=P) the password isassigned to the PROCEDURE-PASSWORD parameter.

FU Output parameterThe function of the structure element

J (Job) The function of this structure element in the net description is toexecute jobs.

P (Procedure) The function of this structure element in the net description is toexecute S procedures.

JOB-ACCOUNT Input/output parameter(BS2000 ENTER parameter).Account number under which the job is billed, see also the USERparameter.

JOB-CAT Input/output parameter(BS2000 ENTER parameter).Parameter for task distribution within an MSCF network (MultiSystem Control Facility); see "AVAS for the Administrator" [3].The target processors are addressed by directly or indirectly speci-fying a catalog ID.If *ANY is specified as the catalog ID, the processor on which AVASis started must belong to an XCS network (see chapter describingmultiprocessor operation with AVAS in “AVAS for the Administrator“[3]).{’catid’ | *ANY | jvname}

Note

In the case of control records for S procedures (P), the host nameassociated with the specified catalog ID is determined when theENTER-PROCEDURE is issued.

JOB-CLASS Input/output parameter(BS2000 ENTER parameter).Job class in which the task is classified.

JOB-DOC Input/output parameter.{*STD | element | *NONE}

Documentation of the task.

U5184-J-Z125-7-76 153


*STD The documentation is sought or stored under the standard name$ugnet_netname.jobname in the DOCLIB.

element Element name for the documentation of the task in the DOCLIB orDOCSYS.$ug_docname$ugsys_docnamedocname


*NONE No documentation is used.If the DOCUMENT operation is entered for the task, the followingmessage is output:AVS4090 THE DOCUMENT FUNCTION IS NOT AVAILABLE

JOB-INDEX Output parameter.indexIndex level of the net at which the task is to run.

JOB-NAME Output parameter.

jobname Name of the task.

JOB-PARAMETER Input parameter(BS2000 ENTER parameter).Specifies additional attributes for the selected job class.If parameters which cannot be defined directly are to be specifiedfor the BS2000 ENTER call, they have to be entered in the form,NAME1=value1,NAME2=value2,...The parameters are then passed upon the ENTER call but notvalidated by AVAS.

JOB-TYPE Output parameter.Type of the structure element.Shows the value for TYPE as entered into mask AVN004, indicatingwhether, and if so in what form, the task is subject to net modifi-cation.(FU=J/P with TYPE=MOD/STD/EXT, FU=P with TYPE=EXX)

154 U5184-J-Z125-7-76


MOD The task is subject to net modification. It was created with CREATE-PROD-NET.

STD The task is not subject to net modification. It must be created withthe CREATE-PROD-NET statement.

EXT The task is not saved in the AVAS system. It is assigned using thefile name specified under ENTER-FILE.


JOB-TEXT Input parameter.Brief text (up to 120 characters) describing the task in greater detail.

LOG Input/output parameter.Indicates whether the SYSOUT log of the tasks in the net is to beprinted out ("Ë", "YES") or not ("NO"), where "Ë" is the blankcharacter.

NET-NAME Output parameter.Name of the net description, to which the structure element forexecuting jobs and S procedures is assigned.

PASSWORD Input parameter.Parameter for the ENTER call of the task, see also the USERparameter. LOGON password for USER (for permissible entries seethe AVN001 mask, NET-PASSWORD parameter). The PASSWORDfield is blanked out in the AVN002 mask.

RESTART-INDEX Input parameter.{index | END}The restart index can be defined for each of the three restartvariants. A restart variant is not possible without this index.

index Index level to be used in the event of a restart (restart of net).A restart is permissible for all index ranges (001 - 999) in allstructure elements, regardless of function and type.

END In the event of a restart (restart of net), the structure element (andall other tasks that are dependent on it) should not be furtherprocessed or checked.The RESTART-NAME parameter is not evaluated in the case of arestart.END must not be specified with restart tasks.

U5184-J-Z125-7-76 155


RESTART-NAME Input parameter.Name for selecting structure elements at the specified restart indexlevel.{name | *ALL | *NAME | *ERROR}

name Only this structure element of the index level specified in RESTART-INDEX will be executed again."name" must be unique at the specified index level.

*ALL All structure elements at the index level specified by RESTART-INDEX are to be executed again.

*ERROR Any structure elements at the restart index level that have the statusERROR are only to be executed again if the RESTART-INDEX is thesame as the ERROR-INDEX.In all other cases, the restart will be rejected.

*NAME Only the structure element at the POINT-OF-ERROR is to beexecuted again. The *NAME parameter is only processed if theRESTART-INDEX is the same as the ERROR-INDEX.In all other cases, the restart will be rejected.

Note

In the event of a restart via index levels 900 through 999, normalprocessing should resume at the index of the POINT-OF-ERROR ifthe parameter RESTART-NAME=*NAME or *ERROR is specifiedunder restart variant 1. In all other cases, the restart will be rejected.

RESTART-TYPE Input parameter.Type of restart processing involved.{RESTART | NORMAL}

RESTART Restart with execution of restart statements #RA, #RI and #RU.

NORMAL Restart without execution of restart statements #RA, #RI and #RU.

Note

Within the range of restart index levels (index 900 through 999), thechangeover from RESTART mode to NORMAL mode can becontrolled by the RESTART-TYPE parameter of restart variant 1.RESTART mode is quit when RESTART-TYPE=NORMAL isspecified under restart variant 1.RESTART mode is quit automatically when the first index level ofnormal processing (index 001 through 899) is processed.

156 U5184-J-Z125-7-76


AUTOMATIC Input parameterType of restart processing{YES | NO}

YES Automatic restart. Restart is initiated automatically, without userinput. Due account is taken of the restart variant selected via#AVJ#RV=n in the errored task.

If a restart variant with AUTOMATIC=YES is used to initiate arestart, AUTOMATIC is reset to NO (as only an automatic restartcan be performed using a restart variant).

If no restart variant has been set via the task job variable, the checkis made in the order RESTART-VARIANT 1, 2, 3.If AUTOMATIC=YES is not specified in the restart variant selectedvia #AVJ#RV=n, the restart will not be initiated automatically (theother variants are not searched for the specificationAUTOMATIC=YES).

NO Manual restart. The restart must be initiated by the RESTART-NETstatement.Modifications to the net can be performed through the MODIFY-SUBMIT-NET and/or MODIFY-SUBMIT-JOB statements.

RESTART-VARIANT Output parameter.Three restart variants are permitted for each task. At least one indexmust be specified for each restart variant if the variant is to bepermitted. The restart is then carried out using the default valuesRESTART-TYPE=RESTART, AUTOMATIC=NO and RESTART-NAME=*ALL, unless other default values have been specifiedthrough the system parameters.

SYNC-INDEX Input/output parameter.Index level at which the task is to be synchronized.{index | NXT | END}

index This value must be greater than the value for JOB-INDEX and mustnot contain an index level from the restart index levels. The systemwaits at this index level for the task to terminate.

NXT The task is synchronized at the next higher index level.

END The task is synchronized at normal end of net (freestanding task).

USER Input/output parameterIdentifier under which the task (job or S procedure) is to run. If aUSER is specified, then the JOB-ACCOUNT and PASSWORDparameters will also be used. All three parameters are taken fromthe net definitions or from the job specification.

U5184-J-Z125-7-76 157


USER-PAR-FILE Input/output parameterFile containing parameters for the modification.{*NONE | *STD | filename | libname(element[,type])}

A USER-PARAM-FILE can only be assigned if the name of thestructure element is no longer than 20 characters (without the usergroup).

*NONE No USER-PARAM-FILE is used.

*STD The name of the USER-PARAM-FILE is sought usingPARAM.$ug.jobname.index in the case of CREATE-PROD-NET.

filename The parameters in this file are used for modifying the job.

libname(element[,type])The parameters are sought in the specified element of the definedlibrary with the specified type of library department.If the type of library department is not specified, type S is used.

The maximum input length is 54 characters.

Note

If specification of a user ID is mandatory (see "AVAS for the Administrator" [3]), specifi-cation of ENTER-PARAMS=NET (mask AVN002) must be accompanied by the entry ofeither a value for USER (mask AVN002) or a value for NET-USER (mask AVN001). Ifthis is not the case, the task will not subsequently be started by the run control systemand will be given the ERROR status.

The same applies if ENTER-PARAMS=LOGON is specified without a user ID in theLOGON statement of the task.

AVN003 - Display and input parameters forstructure elements with FU=C and TYPE=JVA

This mask is used to specify the structure elements for condition control via job variables.

COND-DOC Input/output parameter.{*STD | element | *NONE}

Documentation of the condition.

*STD The documentation is sought or stored under the standard name$ugnet_netname.condname in the DOCLIB.

158 U5184-J-Z125-7-76


element Element name for the documentation of the condition in the DOCLIBor DOCSYS.$ug_docname$ugsys_docnamedocname


*NONE No documentation is used.

If the DOCUMENT operation is entered for the condition, thefollowing message is output:AVS4090 THE DOCUMENT-FUNCTION IS NOT AVAILABLE

COND-INDEX Output parameter.Index level of the net at which the job variable is to be monitored.

COND-NAME Output parameter.Name of the condition description, as specified in mask AVN004.

COND-JVA-NAME Input/output parameter.{jvname | *NONE}

jvname Name of the job variable whose value is to be checked from thespecified position in the specified length. The name must bespecified with both catalog ID and user ID. The job variable must beshareable.

*NONE The condition is regarded as satisfied.

COND-TEXT Input/output parameter.Brief text (up to 120 characters) describing the condition.

COND-TYPE Output parameter.Shows the value for TYPE, as entered via AVN004

JVA The net identified via NET-NAME is meant to wait at the index levelspecified under COND-INDEX until the specified job variablecontains the value specified under COND-VALUE from the specifiedposition and in the defined length.

U5184-J-Z125-7-76 159


COND-VALUE Input/output parameter.

jvvalue Required value of the job variable, to be specified without singlequotes (with COND-TYPE=JVA only). Only C strings may bespecified.

FU Output parameterFunction of the structure element

C (Compare) This element in the net description is a condition, for satisfaction ofwhich the system will wait.

JVA-LENGTH Input/output parameter.

jvlen Length of the value of the job variable to be checked.Default value: 001

JVA-PASSWORD Input parameter.

If the job variable is password-protected, the password must bespecified here.{*NONE | password}

*NONE The job variable is read without a password.

password Format: C´....´: 1 - 4 alphanumeric characters

X´....´: 1 - 8 hexadecimal characters

The field JVA-PASSWORD is blanked on the mask.If the field contents are cleared, *NONE is set.

JVA-POSITION Input/output parameter.

jvpos Position within the value range of the job variable as of which thevalue is to be checked.Default value: 001


index Index level to be used in the event of a restart (restart of net).A restart is permissible for all index ranges (001 - 999) on allstructure elements, regardless of function and type.

END In the event of a restart (restart of net), the structure element (andall other tasks that are dependent on it) should not be furtherprocessed or checked. The RESTART-NAME parameter is notevaluated in the case of a restart.END must not be specified with restart tasks.

160 U5184-J-Z125-7-76



name Only this structure element of the index level specified in RESTART-INDEX will be executed again.

*ALL All structure elements at the index level specified by RESTART-INDEX are to be executed again.

*ERROR Any structure elements at the restart index level that terminatedabnormally (JOB-STATUS=ERROR) are to be executed again. The*ERROR parameter is only processed if the RESTART-INDEX is thesame as the ERROR-INDEX.In all other cases, the restart will be rejected.

*NAME Only the structure element at the POINT-OF-ERROR is to beexecuted again. The *NAME parameter is only processed if theRESTART-INDEX is the same as the ERROR-INDEX.In all other cases, the restart will be rejected.

Note

In the event of a restart via index levels 900 through 999, normalprocessing should resume at the index of the POINT-OF-ERROR ifthe parameter RESTART-NAME=*NAME or *ERROR is specifiedunder restart variant 1. In all other cases, the restart will be rejected.

RESTART-TYPE Input parameter.Type of restart processing involved.{RESTART | NORMAL}


NORMAL Restart without execution of restart statements #RA, #RI and #RU.

Note

Within the range of restart index levels (index 900 through 999), thechangeover from RESTART mode to NORMAL mode can becontrolled by the RESTART-TYPE parameter of restart variant 1.RESTART mode is quit when RESTART-TYPE=NORMAL isspecified under restart variant 1.RESTART mode is quit automatically when the first index level ofnormal processing (index 001 through 899) is processed.

U5184-J-Z125-7-76 161


AUTOMATIC Input parameterType of restart processing{YES | NO}

YES Automatic restart. Restart is initiated automatically, without userinput. Due account is taken of the restart variant selected via#AVJ#RV=n in the errored task.


If no restart variant has been set via the task job variable, the checkis made in the order RESTART-VARIANT 1, 2, 3.If AUTOMATIC=YES is not specified in the restart variant selectedvia #AVJ#RV=n, the restart will not be initiated automatically (theother variants are not searched for the specificationAUTOMATIC=YES).


RESTART-VARIANT Output parameter.Three restart variants are permitted for each task. At least one indexmust be specified for each restart variant if the variant is to bepermitted. The restart is then carried out using the default valuesRESTART-TYPE=RESTART, AUTOMATIC=NO and RESTART-NAME=*ALL, unless other default values have been specifiedthrough the system parameters.

SYNC-INDEX Input/output parameter.Index level at which the system is to wait for the condition to besatisfied (see the AVN002 mask, SYNC-INDEX parameter).

162 U5184-J-Z125-7-76


AVN008 - Display and input parameters forstructure elements with FU=C and TYPE=NET/JOB/RES/VAL

This mask is used to specify structure elements which depend on nets, jobs, resources anddefined values, for use in condition control.

Parameters which have the same meaning in mask AVN008 as in mask AVN003 aredescribed under the latter. Additional parameters, and those which have a differentmeaning, are described here.

COND-NAME Output parameterName of a condition for TYPE=JOB:$ug_jobname1-24Name of the structure element, the status of which is to be tested.If a user group is specified when a condition is tested, it must alwaysbe the user group of the net under which the structure element isexecuted. This applies even if the system user group was specifiedin the condition.

$ug_netname1-12 (TYPE=NET)Name of the net, the status of which is to be tested.

$ug_resname1-24 (TYPE=RES)$ug_valname1-24 (TYPE=VAL)

Note

The name of a condition within an AVAS system must be uniqueacross all condition types.

CONDITION CREATED BYInput/output parameterName and index of the net which created the condition description.If COND-TYPE=RES and VAL, no input is permitted.

NET-NAME {$ug_netname1-12[_date[_time]] | *NONE}The full name of the net with PLAN-START need only be specifiedif the condition description with the smallest positive time differencewith respect to PLAN-START is not to be evaluated, but the one withthe specified PLAN-START is. *NONE may only be specified inconjunction with COND-TYPE=NET.

COND-TYPE=JOBThe user group for the NET-NAME parameter is always the same asthe user group for the COND-NAME parameter.

U5184-J-Z125-7-76 163


COND-TYPE=NETThe specified net name ($ug_netname) must always match thespecified structure element name (COND-NAME). The parameter ispreset to the parameter value NAME from the AVN004 mask.If *NONE is specified, the comparison with the name of the structureelement is omitted and the condition is taken to be satisfied withouta check being performed.

INDEX An index only needs to be specified for a JOB condition if there areseveral descriptions with the same job name and net name.If COND-TYPE=NET is specified, no input is allowed.

ERROR-VALUE Input/output parameter{status | status, ... | c-string | x-string | *NONE}

Event for dependency control

For TYPE=NETThe parameter does not have a preset value.The valid entries are:

For TYPE=JOBThe parameter does not have a preset value.The valid entries are:

For TYPE=RESThe parameter does not have a preset value.The valid entries are:

For TYPE=VALThe format of the entries is subject to the rules described forOCCURE-VALUE.Otherwise, *NONE can be specified from column 1 on. If the inputfield is blank, ERROR-VALUE is given the value *NONE.

ENDED MISSING ABENDED IGNORED

NO-PLAN ABENDED DELETED IGNORED MISSING

ENDED ERROR SKIPPED NO-SUBMIT

MISSING CREATED FREE SHARE ERROR

EXCLUSIVE

164 U5184-J-Z125-7-76


OCCURE-VALUE Input/output parameter{status | status, ... | c-string | x-string}

Event for dependency control

For TYPE=NETIf no entry is made, the parameter is preset with the value ENDED.The valid entries are::

For TYPE=JOBIf no entry is made, the parameter is preset with the value ENDED.The valid entries are:

For TYPE=RESIf no entry is made, the parameter is preset with the value FREE.If the condition is satisfied, the resource is occupied according to thequery.The valid entries are:

For TYPE=VALThe parameter does not have a preset value, but instead an entry isrequested.The parameter can be used to enter values linked by operators.

ENDED MISSING ABENDED IGNORED

NO-PLAN ABENDED DELETED IGNORED MISSING

ENDED ERROR SKIPPED NO-SUBMIT

FREE SHARE SHARE, FREE

FREE If the condition description has the status FREE,the condition is satisfied and the resource isgiven the status EXCLUSIVE.

SHARE If the condition description has the statusSHARE, the condition is satisfied and theresource is given the status SHARE.

SHARE, FREE If the condition description has the statusSHARE or FREE, the condition is satisfied andthe resource is given the status SHARE.

U5184-J-Z125-7-76 165


For condition testing, the following operators are permitted:

Input format:

OP,pos,value(OP,pos,value)(OP,pos,value),(OP,pos,value),...

– OP – comparison operation

If no comparison operation is specified, OP=EQ is assumed. Theparameter and the comma are both omitted (pos,value).

– pos – start position for a value specification

If pos is not specified, pos=1 is assumed.Comparison values with neither OP nor pos are specified directly(value).If a comparison operation is specified without a start position, thecorresponding comma must nevertheless be inserted (OP,,value).

– value – comparison value

Current value of the condition description in the run control file. Thearea comprises 128 bytes.

Note

When a condition description is created, positions for which novalue is assigned are set up with X´40´.

.EQ. .LT. .GT. .LE. .GE. .NE. .OR.

= / EQ - equal to

< / LT - less than

> / GT - greater than

Î / LE - less than or equal to

Ï / GE - greater than or equal to

î / NE - not equal to

nnn

ć-string´

Cć-string´

X´x-string´

166 U5184-J-Z125-7-76


– ),( – logical OR operation

If there are multiple condition tests, their specifications must beenclosed in parentheses, which links them by ORs.

Permissible input formats are:

value(value)(value),(value),...pos,value(pos,value),(pos,value),...OP,pos,value(OP,pos,value)(OP,pos,value),(OP,pos,value),...OP,,value(OP,,value)(OP,,value),(OP,,value),...

These may be combined in any required way, e.g.:

(value),(OP,,value),(pos,value),...

The length of the comparison value is determined by the length ofc-string or x-string, as appropriate.pos + length -1 may not exceed 128.Apostrophes within a c-string must be repeated a second time.

SELECT-RESTART-VARIANTInput/output parameter{1 | 2 | 3}

This parameter is assigned to the ERROR-VALUE parameter.It presets a restart variant to be used in the event of an error.Processing takes place in accordance with the restart variant set forthe jobs by means of the monitor job variable.If no entry is made here, the restart variants for the condition aresearched for AUTOMATIC=YES, as in the case of jobs, and if arestart variant is found this is used to automatically initiate a restart.If no restart variant with AUTOMATIC=YES is found, the restartmust be initiated by the RESTART-NET statement.

U5184-J-Z125-7-76 167


AVN009 - Display and input parameters forstructure elements with FU=X and TYPE=STD/MOD/EXT

This mask is used to specify structure elements for executing server jobs.

The mask is displayed in various formats, depending on the type of structure elementspecified:If TYPE=EXT, the FILENAME input field is displayed; if TYPE=MOD, the USER-PAR-FILEinput field is displayed.

Otherwise the structure of the mask is identical in all formats.

The SERVER job is started and monitored on the BS2000 host by an AVAS utility routine.This BS2000 task is referred to below as the AVAS agent AVSSINCM.

ENTER-PARAMS Output parameter.Origin of the parameters for the call which starts this task.

NET The ENTER parameters from the net description are adopted.

FILENAME Input/output parameter.Name of the file to be started in the server system if JOB-TYPE=EXT. The file must be available on the server system. Thepath containing the file is defined by the entry “dir” in the configu-ration file and is extended via directory specifications in this field(see also “AVAS for the Administrator“ [3]).

FU Output parameter.Function of the structure element.

X (SV job) This element in the network description is a structure element forthe execution of SV jobs.

JOB-ACCOUNT Input/output parameter.(BS2000 ENTER parameter)Account number under which the activities of the AVAS agentAVSSINCM are recorded.

JOB-CAT Input/output parameter.(BS2000 ENTER parameter)Parameter for task distribution within a HIPLEX MSCF network (see“AVAS for the Administrator“ [3]).

The host on which AVSSINCM is to run is addressed via direct orindirect specification of a catalog ID.{’catid’ | jvname}

JOB-CLASS Input/output parameter.(BS2000 ENTER parameter)Job class in which AVSSINCM is put.

168 U5184-J-Z125-7-76


JOB-DOC Input/output parameter.{*STD | element | *NONE}

Documentation of the SV job.

*STD The documentation is sought or saved under the default name$ugnet_netname.jobname in the DOCLIB.

element Element name for the documentation of the task in the DOCLIB orDOCSYS.$bk_docname$bksys_docnamedocname

docname can have up to 37 characters. If no user group is specified,the documentation is sought under the user group of the net in theDOCLIB. If $ugsys is specified, the documentation is sought in theDOCSYS.The DOCUMENT operation allows only those elements to beprocessed for which the user group of the documentation elementis the same as the user group of the net. Elements which do notbelong to the user group can be read but not written back. The inputof NEW-DOCUMENT-NAME via mask AVS016 is expected.

*NONE No documentation is used.If the DOCUMENT operation is entered for the task, the followingmessage is output:AVS4090 THE DOCUMENT FUNCTION IS NOT AVAILABLE

JOB-INDEX Output parameter.Index level of the task.index

JOB-NAME Output parameter.

jobname Name of the task.

JOB-PARAMETER Input parameter.(BS2000 ENTER parameter)Additional parameters for the BS2000 ENTER call for startingAVSSINCM.If parameters which cannot be defined directly are to be specifiedfor the BS2000 ENTER call, they must be entered in the format,NAME1=value1,NAME2=value2,.... The parameters are notchecked by AVAS and are passed with the ENTER call.

JOB-TEXT Input parameter.Short text of up to 120 characters describing the task.

U5184-J-Z125-7-76 169


JOB-TYPE Output parameter.Type of the structure element.Shows the value specified in mask AVD004 for TYPE, indicatingwhether the task is subject to net modification, and in what form.

MOD The task is subject to net modification. It will be created by aCREATE-PROD-NET statement.

STD The task is not subject to net modification. It must be created by aCREATE-PROD-JOB statement.

EXT The task is not saved in the AVAS system. It is assigned with the filename specified under FILENAME.

LOG Input/output parameter.Specifies whether the SYSOUT log of AVSSINCM is also to beprinted in a listing: “Ë“, “YES“ or “NO“(Ë = space character).

NET-NAME Output parameter.Name of the net description to which the structure element forexecuting SV jobs is assigned.

PASSWORD Input parameter.Parameter for the ENTER-PROC call of AVSSINCM, see also theUSER parameter. LOGON password for USER (for permissibleentries, see mask AVN001 NET-PASSWORD). The PASSWORDfield is blanked out in mask AVN009.


index Index level to be used in the event of a restart (of the net).Restart is permissible for all index levels (001 - 999) on all structureelements, regardless of the function and the type.

END The structure element and all tasks dependent on it will not beprocessed or checked any further in the event of a restart.The RESTART-JOB-NAME parameter is not evaluated.END cannot be specified for restart tasks.

170 U5184-J-Z125-7-76



name Only this structure element on the index level specified in RESTART-INDEX will be processed again.name must be unique on the specified index level.

*ALL All structure elements at the index level specified in RESTART-INDEX are to be processed again.

*ERROR All structure elements at the restart index level which have thestatus ERROR are to be processed again.*ERROR will only be processed if RESTART-INDEX is identical toERROR-INDEX.Otherwise, the restart will be rejected.

*NAME Only the structure element in the POINT-OF-ERROR is to beprocessed again. *NAME will only be processed if RESTART-INDEXis identical to ERROR-INDEX.Otherwise, the restart will be rejected.

Note

When a restart takes place at index levels 900 to 999, normalprocessing must resume at the index of the POINT-OF-ERROR ifRESTART-NAME=*NAME or *ERROR is specified for restart variant1.Otherwise, the restart will be rejected.

RESTART-TYPE Input parameter.Type of restart processing.{RESTART | NORMAL}


If an SV job is restarted with RESTART-TYPE=RESTART, thismeans:Before AVSSINCM is started, the run control system returns thecontents of the server area (positions 129 - 256) of the last run tothe task job variable. AVSSINCM recognizes from the contentswhether the job must be restarted (start mode of AVSSINCM) orwhether the status of the SV job is to be obtained (QUERY mode ofAVSSINCM).

U5184-J-Z125-7-76 171


NORMAL Restart without processing of restart statements #RA, #RI and #RU.

If an SV job is restarted with RESTART-TYPE=NORMAL, thismeans:AVSSINCM is restarted and branches to start mode. The contentsof the job variables (of the last run) are deleted.

Note

In the range of restart index levels (900 through 999), the transitionfrom RESTART mode to NORMAL mode can be controlled bymeans of the RESTART-TYPE parameter of restart variant 1. Thejob leaves the RESTART mode if RESTART-TYPE=NORMAL isspecified for restart variant 1.The job automatically leaves RESTART mode once the first indexlevel of regular processing (index 001 through 899) has beenprocessed.

AUTOMATIC Input parameterType of restart processing.{YES | NO}

YES Automatic restart. Restart is initiated automatically, without userinput. Due account is taken of the restart variant selected viaAVSSINJV ´RV=n´ in the errored task (equivalent to #AVJ#RV=n inBS2000).


If no restart variant has been set, the check is made in the orderRESTART-VARIANT 1, 2, 3.If AUTOMATIC=YES is not specified in the restart variant selectedvia #AVJ#RV=n, the restart will not be initiated automatically (theother variants are not searched for the specificationAUTOMATIC=YES).


172 U5184-J-Z125-7-76


RESTART-VARIANT Output parameter.Three restart variants are permitted for each task. At least the indexmust be specified for each restart variant if the variant is to bepermitted. The restart is then carried out using the default valuesRESTART-TYPE=RESTART, AUTOMATIC=NO and RESTART-NAME=*ALL, unless other default values have been specifiedthrough the system parameters.

SERVER-NAME Input/output parameter.Symbolic name of a server user ID on a server system{*STD | name}

*STD By default, the SERVER-NAME defined for the user group in thesystem parameters is assigned via the CREATE-PLAN-NETstatement.If no SERVER-NAME is defined in the user group data (*NONE), theplanning of the net is rejected.

name Symbolic name of a server user ID. The name of the server system,the real server user ID and other specifications for the execution ofthe SV job are taken from the SERVER-NAME entry in the configu-ration table (see “AVAS for the Administrator“ [3]).

SERVER-PASSWORDInput/output parameter.Password with which users prove to AVAS that they are authorizedto use the entry SERVER-NAME.{*NONE | password}

*NONE No password is used.

password File passwordFormat: C´........´ or ´........´: 1 - 8 alphanumeric characters.

SYNC-INDEX Input/output parameter.Index level at which the task is to be synchronized.{index | NXT | END }

index The value of SYNC-INDEX must be greater than the value definedfor JOB-INDEX. Index levels of a restart job cannot be specified.At this index level, the system waits for the end of the task.

NXT The task is synchronized at the next index level up.

END The task is synchronized when the net is terminated normally(freestanding task).

U5184-J-Z125-7-76 173


USER Input/output parameter.BS2000 user ID under which AVSSINCM is to run.If USER is specified, the JOB-ACCOUNT and PASSWORD param-eters are also used. All three parameters are taken from the netdefinitions or from this description.

Note

The BS2000 user ID specified under USER must have access to theconfiguration file (see “AVAS for the Administrator“ [3]).

USER-PAR-FILE Input/output parameterFile containing parameters for modifying the job with TYPE=MOD.{*NONE | *STD | filename | libname(element[,type])}

A USER-PARAM-FILE can only be assigned if the name of thestructure element is no longer than 20 characters (without the usergroup).

*NONE No USER-PARAM-FILE is used.

*STD The name of the USER-PARAM-FILE is sought usingPARAM.$ug.jobname.index in the case of CREATE-PROD-NET.

filename The parameters in this file are used for modifying the job.

libname(element[,type])The parameters are sought in the specified element of the definedlibrary with the specified type of library department.If the type of library department is not specified, type S is used.

The maximum input length is 54 characters.

AVN030 - Display and input parameters forstructure elements with FU=A/M/D and TYPE=RES/VAL

This mask is used to specify structure elements for creating, modifying and deletingresources and defined values. Parameters which have the same meaning in mask AVN030as in mask AVN003 are described under the latter. Additional parameters, and those whichhave a different meaning, are described here.

COND-VALUE Input/output parameterStatus (for TYPE=RES) or value (for TYPE=VAL) of the conditiondescription. For FU=D, no status or value can be defined.The condition description in the run control file is modified by thepredefined status.

174 U5184-J-Z125-7-76


For TYPE=RESPermissible entries:

For TYPE=VALvaluepos,value(value)(pos,value)(pos,value),(pos,value),...

or in combinations, e.g.:

(value),(pos,value),...

A corresponding entry is made in the condition description in the runcontrol file.

For the function A (Add), any positions which are not defined aregiven the value X´40´.

Note

When condition descriptions are created, no check is made onoverlaps.

FU TYPE Status Meaning

A RES CREATED The resource is not yet available.

FREE The resource is available.

ERROR The resource is not available.

SHARE The resource is created and used by the netin SHARE mode.

EXCLUSIVE The resource is created and used by the netin EXCLUSIVE mode.

D RES A resource can only be deleted(FU=D,TYPE=RES) if it has the status FREE(no net is using the resource) or CREATEDor ERROR and no net is waiting for theresource to be allocated.

M RES FREE If the resource is being used by the net it isreleased, or its status is reset fromCREATED or ERROR to FREE.

CREATED The resource can no longer be used, orcannot yet be used.

ERROR The resource can no longer be used,because an error has occurred.

U5184-J-Z125-7-76 175

CREATE-NET-DESCRIPTION Masks AVN031/AVN032

AVN031 - Display and input parameters forstructure elements with FU=D and TYPE=NET/JOB

This mask is used to specify structure elements for deleting NET and JOB type conditiondescriptions.


CONDITION CREATED BYInput/output parameterName and index of the net which created the condition description.

NET-NAME $ug_netname1-12[_date[_time]]The full name of the net with PLAN-START need only be specifiedif the condition description with the smallest positive time differencewith respect to PLAN-START is not to be deleted, but the one withthe specified PLAN-START is.

COND-TYPE=JOBThe user group for the NET-NAME parameter is always the same asthe user group for the COND-NAME parameter.

COND-TYPE=NETThe specified net name ($ug_netname) must always match thespecified structure element name (COND-NAME). The parameter ispreset to the parameter value NAME from the AVN004 mask.

INDEX An index only needs to be specified for a JOB condition if there areseveral descriptions with the same job name and net name.If COND-TYPE=NET is specified, no input is allowed.

AVN032 - Display and input parameters forstructure elements with FU=W and TYPE=TIM

This mask is used to specify structure elements for timed waits.

The parameters of mask AVN032 are as described for mask AVN003.

The wait time is defined by display and entry of the plan data (mask AVM023).

176 U5184-J-Z125-7-76

Masks AVN021 CREATE-NET-DESCRIPTION

AVN021 - Display and input plan data forstructure elements with FU=J/P/X and TYPE=STD/MOD/EXT/EXX

Mask AVN021 enables plan data to be defined, deleted or modified for a job, an SV job oran S procedure (task). A maximum of 50 SYMDAT entries can be defined.

The parameters LATEST-START, DELAY-SOLUTION and LIFE-TIME must be specified foreach SYMDAT description.These specify– the latest time at which the task should be started,– the behavior if this time is passed, and– whether a condition description is to be entered in the run control file when the net is

released.

DELAY-SOLUTION Input/output parameterMeasure to be taken if the start is not timely (LATEST-START ispassed).{START | IGNORE | CANCEL}

If nothing is specified, the value defined for DEFAULT-JOB-DELAYvia the generation parameters is used.

START The task should be started.

IGNORE The task should not be started.

CANCEL The task will not be started, and is considered to have terminatedabnormally.

The job status and net status after the LATEST-START time hasbeen passed depend on the DELAY-SOLUTION parameter:


J (Job) This element of the net description is a structure element forexecuting jobs.

P (Procedure) This element of the net description is a structure element forexecuting S procedures.

X (SV job) This element of the net description is a structure element forexecuting SV jobs.

DELAY-SOLUTION JOB-STATUS NET-STATUS

STARTIGNORECANCEL

RUNNINGIGNOREDERROR

RUNNINGRUNNINGERROR

U5184-J-Z125-7-76 177


JOB-INDEX Output parameterIndex level of the net at which the task is to run.index

JOB-NAME Output parameter

jobname Name of the task

JOB-TYPE Output parameter.Type of the structure element.Shows the value for TYPE as entered into mask AVN004, indicatingwhether the task is subject to net modification, and if so in whatform.(FU=J/P with TYPE=MOD/STD/EXT, FU=P with TYPE=EXX)

MOD The task is subject to net modification. It is created with CREATE-PROD-NET.

STD The task is not subject to net modification. It was not created withCREATE-PROD-NET.

EXT The task is not managed via AVAS. It is assigned using the file namespecified under ENTER-FILE or FILENAME.


JOB-TEXT Output parameterBrief text (up to 120 characters) describing the task in greater detail.

LATEST-START Input/output parameterLatest start time for the task, relative to the planned start time in thenet name (PLAN-START).{nnn.hh.mm | *nn.hh.mm | *NONE}

nnn.hh.mm Date and time span relative to PLAN-START.nnn is the number of calendar days, in the range 000 to 999.

*nn.hh.mm Date span relative to PLAN-START, and absolute time.nn is the number of calendar days, from 00 to 99

*NONE The task can be started with any required delay.

If no entry is made, *NONE is assumed. The value which will beused for *NONE is that specified for DEFAULT-LATEST-JOBSTARTvia the generation parameters.

178 U5184-J-Z125-7-76


LIFE-TIME Input/output parameterThe lifetime of the “job end” event for this job. When the run controlfile is reorganized, this event entry will not be deleted until thisinterval of time has elapsed. If the time has elapsed and the evententry has still not been deleted, any subsequent test will be unableto find it.The lifetime is relative to the value of PLAN-START.{nnn.hh.mm | *NONE}

nnn.hh.mm When the net is released by a SUBMIT-NET or REPEAT-NET, acondition description for the task is entered into the run control file.The time interval is relative to PLAN-START, and is equal to nnncalendar days, hh hours and mm minutes.

*NONE When the net is released by a SUBMIT-NET or REPEAT-NET, nocondition description for the task is entered into the run control file.

M Input parameterMark column for selecting plan data.

D (Delete) The marked plan data items are deleted.

Y (Yes) The value shown in mask AVN021 for the plan date can be modified.

N (No) All unmarked items of plan data can be modified.

Note


NET-NAME Output parameterName of the net description, to which the structure element forexecuting jobs, SV jobs and S procedures is assigned.

SELECT-TURNUS Input parameterCharacteristic used in selecting the task when planning theprocessing of the net.

Permissible values are the digit 0 or a subset of the digits 1 to 9. If0 is specified, the job will always be brought to execution.

The task will be brought to execution if the value assigned at theplanning stage is identical to one of the SELECT-TURNUS valuesfor the task.

U5184-J-Z125-7-76 179


Note

If SELECT-TURNUS and SYMDAT are used for selecting structureelements when planning nets, a structure element will only beselected if both selection criteria are satisfied.

SYMDAT Input/output parameterCharacteristic used in selecting the task when planning theprocessing of the net.{*NONE | *STD | symdat}

*NONE If the net is planned without a symbolic start time (plan with noSYMDAT-NAME), then LATEST-START, DELAY-SOLUTION andLIFE-TIME are set by this entry.The parameter *NONE is a default value which cannot be deleted.*NONE is only permitted as the first entry.

*STD The structure element is always selected during planning.The associated planning parameters are copied from this entry.*STD is only permitted as the second entry.Subsequent entries may contain symbolic start dates, but these arenot used in planning if the second entry is *STD.

symdat When a symbolic start time, SYMDAT-NAME, is used in planning thenet, the structure element is selected if the symbolic start timeprescribed for the plan is specified for the structure element.In producing the plan, the assigned plan parameters LATEST-START, DELAY-SOLUTION and LIFE-TIME are then used.This entry is only used if the second entry is not *STD.

Note

For the structure elements, the first entry under SYMDAT isgenerated with *NONE.

The second entry may be either *STD or symdat. For the third to51st entries, only symdat is permitted.If *STD is specified for the second entry, none of the followingentries will be used in planning.

180 U5184-J-Z125-7-76

Masks AVN022 CREATE-NET-DESCRIPTION

AVN022 - Display and input plan data forstructure elements with FU=C and TYPE=JVA/NET/JOB/RES/VAL

Mask AVN022 enables plan data to be defined, deleted or modified for a condition whichperforms a test. A maximum of 50 SYMDAT entries can be defined.

The parameters LATEST-OCCURE and DELAY-SOLUTION must be specified for eachSYMDAT description.The LATEST-OCCURE parameter is not tested until all the dependencies have beenresolved, this being the earliest time at which the condition needs to be checked.

COND-INDEX Output parameterIndex level of the net at which the condition is to be monitored.

COND-NAME Output parameterName of the condition description, as specified in mask AVN004.

COND-TEXT Output parameterBrief text (up to 120 characters) describing the condition.

COND-TYPE Output parameterShows the value for TYPE, as entered via AVN004.{NET | JOB | RES | VAL | JVA}

DELAY-SOLUTION Input/output parameterMeasure to be taken if the test is not timely (LATEST-OCCURE ispassed).{START | IGNORE | CANCEL}

If nothing is specified, the value defined for DEFAULT-CONDITION-DELAY via the generation parameters is used.

START The condition is satisfied.

IGNORE The condition is ignored and net processing is continued.

CANCEL The ERROR status is set for the condition.Net processing must be continued by a restart.

After LATEST-OCCURE has been passed, the condition status andthe net status depend on the DELAY-SOLUTION parameter:

DELAY-SOLUTION COND-STATUS NET-STATUS

STARTIGNORECANCEL

OCCURREDIGNOREDERROR

RUNNINGRUNNINGERROR

U5184-J-Z125-7-76 181



C (Compare) This element of the net description is a condition which performs atest.

LATEST-OCCURE Input/output parameterThe latest point in time for the satisfaction of the condition, relativeto the planned start time in the net name (PLAN-START).{nnn.hh.mm | *nn.hh.mm | *NONE}

nnn.hh.mm Date and time span relative to PLAN-START.nnn is the number of calendar days, from 000 to 999.

*nn.hh.mm Date span relative to PLAN-START, and absolute time.nn is the number of calendar days, from 00 to 99

*NONE Any delay in the satisfaction of the condition can be accepted.

If no entry is made, *NONE is assumed. The value which will beused for *NONE is that specified for DEFAULT-LATEST-START viathe generation parameters.

M Input parameterMark column for selecting plan dates.

D (Delete) The marked plan date is deleted.The first entry with SYMDAT=*NONE cannot be deleted.

Y (Yes) The value shown in mask AVN022 for the plan date can be modified.

N (No) All unmarked plan dates can be modified.

Note


SELECT-TURNUS Input/output parameterCharacteristic used in selecting the condition when planning theprocessing of the net.

Permissible values are the digit 0 or a subset of the digits 1 to 9. If0 is specified, the condition will always be selected.

The condition will be selected if the value assigned at the planningstage is identical to one of the SELECT-TURNUS values for thetask.

182 U5184-J-Z125-7-76


Note

If SELECT-TURNUS and SYMDAT are used for selecting structureelements when planning nets, a structure element will only beselected if both selection criteria are satisfied.

SYMDAT Input/output parameterCharacteristic used in selecting the condition when planning theprocessing of the net.{*NONE | *STD | symdat}

*NONE If the net is planned without a symbolic start time (plan with noSYMDAT-NAME), then LATEST-OCCURE and DELAY-SOLUTIONare set by this entry.The parameter *NONE is a default value which cannot be deleted.*NONE is only permitted as the first entry.


symdat When a symbolic start time, SYMDAT-NAME, is used in planning thenet, the structure element is selected if the symbolic start timeprescribed for the plan is specified for the structure element.In producing the plan, the assigned plan parameters LATEST-OCCURE and DELAY-SOLUTION are then used.This entry is only used if the second entry is not *STD.

Note

For the structure elements, the first entry under SYMDAT isgenerated with *NONE.The second entry may be either *STD or symdat. For the third to51st entries, only symdat is permitted.If *STD is specified for the second entry, none of the followingentries will be used in planning.

U5184-J-Z125-7-76 183


AVN023 - Display and input plan data forstructure elements with FU=W and TYPE=TIM

Mask AVN023 enables plan data for a timed wait to be defined, deleted or modified. Amaximum of 50 SYMDAT entries can be defined.

The OCCURE-TIME parameter must be specified for each SYMDAT entry (OCCURE-DATE).CREATE-PLAN-NET copies OCCURE-DATE and OCCURE-TIME into the name of theentry.

No condition description is entered into the run control file.


COND-NAME Output parameterName of the structure element


W (Wait) This element of the net description is a structure element for timedwaits.

OCCURE-DATE This is defined by the SYMDAT parameter when the net is planned.

SYMDAT Input/output parameterCharacteristic used in selecting the condition when planning theprocessing of the net.{*NONE | *STD | symdat}

*NONE If the net is planned without a symbolic start time (plan with noSYMDAT-NAME), then OCCURE-TIME is set by this entry.The parameter *NONE is a default value which cannot be deleted.*NONE is only permitted as the first entry.


symdat When a symbolic start time, SYMDAT-NAME, is used in planning thenet, the structure element is selected if the symbolic start timeprescribed for the plan is specified for the structure element.

184 U5184-J-Z125-7-76


In producing the plan, the assigned OCCURE-TIME plan param-eters are then used.This entry is only used if the second entry is not *STD.

Note

For the structure elements, the first entry under SYMDAT isgenerated with *NONE.The second entry may be either *STD or symdat. For the third to51st entries, only symdat is permitted.If *STD is specified for the second entry, none of the followingentries will be used in planning.

OCCURE-TIME Input/output parameter{nnn.hh.mm | *nn.hh.mm | *NONE}

nnn.hh.mm Time, specified relative to PLAN-START-DATE andPLAN-START-TIMEThe system waits until PLAN-START-DATE + nnn days andPLAN-START-TIME + hh.mm hours and minutes.

*nn.hh.mm Absolute time specificationThe system waits until PLAN-START-DATE + nn days anduntil the time is hh.mm.

*NONE The system waits for a random amount of time.

If no entry is made, *NONE is assumed. The value which will beused for *NONE is that specified for DEFAULT-OCCURE-TIME viathe generation parameters.

Note

CREATE-PLAN-NET copies OCCURE-DATE and OCCURE-TIMEinto the name of the condition if the latter was specified with *DATE.Conversion: plan start of the net + *nn.hh.mm, or nnn.hh.mm

U5184-J-Z125-7-76 185


AVN024 - Display and input plan data forstructure elements with FU=A/M/D and TYPE=RES/VALor with FU=D and TYPE=NET/JOB

Mask AVN024 enables plan data to be defined, deleted or modified for a description (for acondition description in the run control file). A maximum of 50 descriptions can be defined.


SYMDAT Input/output parameter{*NONE | *STD | symdat}Symbolic date for selecting the task.

Note

For the structure elements, the first entry of a SYMDAT is generatedwith *NONE.This ensures that the structure element is executable when the netis started without a symbolic start date.This entry cannot be deleted.

Either *STD or symdat is permitted as the second entry.

In the case of *STD, the structure element is always selected.

For the third to 51st entries, only symdat is permitted.

186 U5184-J-Z125-7-76

MODIFY-NET-DESCRIPTION

MODIFY-NET-DESCRIPTIONModify net description

The MODIFY-NET-DESCRIPTION statement can be used to modify existing net descrip-tions in the NETLIB.

It can be used to

– modify net parameters– modify net plan data– add, modify or delete net masks– add, modify or delete structure elements.

Using the overview masks, the user selects individual objects or has them displayed directlyby specifying "OBJ".

The MODIFY-NET-DESCRIPTION statement can call the CHECK function through theCHECK operation in the masks AVN001, AVN004, AVN006 and AVN020.The checks that the CHECK function performs are described in the section dealing with theCHECK function in the manual “AVAS for the Administrator” [3].

NET-NAME=Name of a net whose net description is to be modified.

NET-NAME=$ug_Name of the user group.If no user group is specified, all elements of the user’s own user group are displayed.

NET-NAME=netnameElement name in the NETLIB.Depending on the OBJECT operand, this input directly causes the net description to beprocessed.

If the net name is entered via a partial qualification (final character *), an overview isdisplayed of those elements whose names begin with the partial qualification.

If no net name is entered, all elements of the specified user group are displayed.

MODIFY-NET-DESCRIPTION

[NET-NAME=[$ug_ ]netname]


U5184-J-Z125-7-76 187

MODIFY-NET-DESCRIPTION Mask AVN011

OBJECT=Selection of the mask for modifying data in net descriptionsIf OBJECT is not specified, OBJECT=NET is used as the default setting, and mask AVN001is presented.

OBJECT= NETMask AVN001 is to be presented for modifying the net parameters.

OBJECT=PSTMask AVN020 is to be presented for modifying the net plan data.

OBJECT= MAPMask AVN006 is to be presented for modifying the net mask table.

OBJECT= STRMask AVN004 is to be displayed for modifying the structure elements.

AVN011 - Overview of net descriptions from the net library


IND;OBJ Input/output parameter.This is only processed in connection with the S mark.{index | NET | PST | MAP | STR}

index Entering "index" causes an overview to be displayed containing thestructure elements starting at the desired index level. Withindex=000 the overview starts with the first structure element. IfOBJECT was not specified, the default value for CMD:EXECUTE isSTR.

NET Mask AVN001 is presented for net data modification.

PST Mask AVN020 is presented for modification of the net plan data.

MAP Mask AVN006 is presented with the overview of net parameter inputmasks for modification.

STR Mask AVN004 is presented with the overview of the structureelements.

M Input parameter.

S (Select) The marked net description is selected for modification.The marks N and Y are prohibited here.

NET-NAME Output parameter.$ug_netnameNames of the net descriptions presented for modification.

188 U5184-J-Z125-7-76

Masks AVN001/AVN020/AVN006 MODIFY-NET-DESCRIPTION


UPDATED The net description was modified.

WARNING The net description was modified.

CHECK discovered errors in the net description. A report has beengenerated.

AVN001 - Display net parameters for modification

The parameters of the AVN001 mask are described under the CREATE-NET-DESCRIPTION statement. Apart from NET-PASSWORD, all input parameters fromCREATE-NET-DESCRIPTION are now input/output parameters.

Note

When processing nets of a foreign user group, a user can only change the RUN-CONTROL-SYSTEM parameter to the run control system assigned to his own usergroup. Any other modification of this parameter requires the appropriate authorization.

A branch to the other masks can be effected via CONTINUE (mask AVN020, OBJ=PST) orthe operand OBJ=MAP/STR (masks AVN006/AVN004).

AVN020 - Display net plan data for modification

The parameters of mask AVN020 are described under the CREATE-NET-DESCRIPTIONstatement.

CONTINUE displays mask AVN006.

If it is required to immediately define structure elements (mask AVN004), OBJECT=STRmust be entered into the operand field.

AVN006 - Table of net masks for entering net parameters

The parameters for mask AVN006 are described under the CREATE-NET-DESCRIPTIONstatement.

Entering CONTINUE causes the AVN004 to be displayed.

A branch to masks AVN004, AVN001 or AVN020 can be effected by specifyingOBJECT=STR/NET/PST in the operand field.

U5184-J-Z125-7-76 189

MODIFY-NET-DESCRIPTION Mask AVN004

AVN004 - Display net structure for modification of structure elements

Mask AVN004 can be used to modify, delete and add structure elements.

Modifying:

After selection by marking with Y, all displayed parameters of the selected elements can bemodified. To modify element parameters not shown in the display, the element must bemarked with S, after which the remaining parameters of the structure element may bemodified via the assigned masks. To enable the descriptions of the structure elements to bemodified NEXT=DES should be specified, and NEXT=SYM for the plan data in the structureelements.Note that it is not permitted to enter different markings. If the mask is sent off withEXECUTE but without markings, all the lines may be modified.

Note

For defined structure elements, a modification of the function FU will result in all theassigned parameter values being deleted. New default values will be assigned, thesedepending on the function and type.

Exception

When the function is modified from J to P or vice versa, the defined parameter valuesare retained.

Deleting:

Structure elements are deleted by marking them with D.

Adding:

Structure elements are inserted or appended by entering the displayed parameters in ablank line of the mask. To define a new element, at least the parameters IND (index), FU(function), TYPE and NAME of the structure element must be entered. The descriptions ofthe net structure can be marked with S if it is required to complete additional parameters.


M Input parameter.Mark column for selecting the structure elements to be processed.

S (Select) Selects the structure element to be defined by further parameters orwhose parameters are to be modified. The corresponding mask,which depends on the parameters FU, TYPE and NEXT, isdisplayed after entering EXECUTE.

D (Delete) The marked structure element is deleted from the net description.

190 U5184-J-Z125-7-76

Mask AVN004 MODIFY-NET-DESCRIPTION

Y (Yes) The structure element values displayed via mask AVN004 can bemodified.

N (No) All unmarked structure elements can be modified.

The data in all the displayed structure elements can be modifiedafter entering EXECUTE, without having to enter any marks.

Note

In connection with the D, Y and N marks, the work window cannotbe repositioned.If the EXECUTE operation is entered together with a + or - mark,the structure elements of the repositioned work window arepresented for modification.

U5184-J-Z125-7-76 191

CHANGE-NET-DESCRIPTION

CHANGE-NET-DESCRIPTIONGlobal changes to nets

The CHANGE-NET-DESCRIPTION statement can be used to make global changes to netsin the user library NETLIB. In addition, changes to USER, ACCOUNT and PASSWORD canbe passed to the run control system so that the new signon information can also beassigned to the nets that have already been planned and released for processing.

The following BS2000 parameters can be changed using CHANGE-NET-DESCRIPTION:

USER, PASSWORD, LOG, ACCOUNT, CLASS, CAT

Both the old and new values for the parameters to be modified have to be entered. Thefollowing functions are available:

Parameters will only be modified if all the "OLD" values specified correspond exactly withtheir existing values held in the net description (AND operation on all parameters specified).

If a parameter is not to be modified, its new value must be identical to its old.

The modifications are performed in all selected net descriptions and all job descriptions.

A net overview is displayed in the AVN011 mask when the statement is executed.Nets to be included in this process can be selected using the Y and N marks.

Any BS2000 parameters that are to be changed in net descriptions must be marked.

The AVN007 mask for entering the change data is displayed following the EXECUTEoperation.Processing is started or canceled using the CONTINUE or RETURN operation on AVN007.The outcome of the operation on each net is displayed in the RESULT field of the AVN011mask.

NET-NAME=Name of a net in the NPRLIB whose parameters are to be modified.

– modify parameter: OLD-para=value NEW-para=value

– delete parameter: OLD-para=value NEW-para=*DEL

– insert parameter: OLD-para=*INS NEW-para=value

CHANGE-NET-DESCRIPTION


192 U5184-J-Z125-7-76

Mask AVN011 CHANGE-NET-DESCRIPTION

NET-NAME=$ug_Name of user groupIf no user group is specified, the operator’s user group will be used.The only users permitted to specify a different user group to the one to which they belongare privileged users.

NET-NAME=netnameElement name in the NETLIBIf the net name includes a wildcard symbol (final character is a *), all elements whosenames match the specified part of the name will be displayed.

If the statement is issued without an operand, NET-NAME=$ug_* and the operator’s usergroup will be assumed.

A net overview will always be displayed in the mask AVN011, irrespective of which operandsand values are entered.


DATE Output parameterDate of last change

IND;OBJ The parameter is irrelevant here.

M Input parameter

Y (Yes) The marked net is to be processed.

N (No) All net descriptions except those marked N are to be processed.

No other types of mark are permitted.The AVN007 mask for entering the change data is displayedfollowing the EXECUTE operation.Any BS2000 parameters that are to be changed in net descriptionsmust be marked.If no nets are marked, the changes made on mask AVN007 are onlyused for the run control system.

NET-NAME Output parameter$ug_netnameName of the net to be modified.


CHANGED At least one parameter in the net was modified.

U5184-J-Z125-7-76 193

CHANGE-NET-DESCRIPTION Mask AVN007

NO-CHANGE Net not modified. The data in the net is not identical with that in theOLD-... parameter.

ERROR The net cannot be processed. The structure of the net is invalid.

NOT-FOUND The net no longer exists.

LOCKED The net is locked.

Mask AVN007 - Entry of parameters to be changed

OLD-USER==value User ID that is to be changed in the net description.

=*INS If there is no user ID in the net description, *INS must be specified.

NEW-USER==value New user ID.

=*DEL The user ID in the net description will be deleted (replaced withblanks).

The USER parameter will only be changed if the PASSWORDparameter is also specified.

OLD-PASSWORD==value Password that is to be changed in the net description.

To change the password, the existing one must be entered in full.

=*INS If there is no password in the net description, *INS must bespecified.

NEW-PASSWORD==value New password

=*DEL The password in the net description will be deleted (replaced withblanks).

The PASSWORD parameter will only be changed if the USERparameter is also specified.

OLD-ACCOUNT==value Account number that is to be changed in the net description.

=*INS If there is no account number in the net description, *INS must bespecified.

NEW-ACCOUNT==value New account number

=*DEL The account number in the net description will be deleted (replacedwith blanks).

194 U5184-J-Z125-7-76

Mask AVN007 CHANGE-NET-DESCRIPTION

RETENTION-PERIOD=The RETENTION-PERIOD operand is only available on the batchinterface.

=*NONE Changes to USER, ACCOUNT and PASSWORD should only beentered in the net description for NETLIB.If *NONE is specified, nets must be marked on the AVN011 mask.

=nnn.hh.mm In addition to the changes in the NETLIB (see *NONE), the data forthe run control system is stored with a retention period as a relativedate and a relative time span based on the processing datedisplayed in the mask.nnn (000 to 999) is the number of calendar days in the retentionperiod.

=*nn.hh.mm In addition to the changes in the NETLIB (see *NONE), the data forthe run control system is stored with a retention period as a relativedate span and an absolute time based on the processing datedisplayed in the mask.nn (00 to 99) is the number of calendar days in the retention period.

Changes for the run control system only come into effect whenthese changes are made known to the run control system by an/INTR-RESUME command from the AVAS administrator.

Note

RETENTION-PERIOD defines

– the length of time for which this OLD/NEW conversion of the runcontrol system will be performed

– how long the transition time (retention period) lasts until theOLD data can again be entered with other NEW data in the caseof CHANGE-NET-DESCRIPTION

– how long the transition time (retention period) lasts until theNEW data can again be specified as OLD data for the nextCHANGE-NET-DESCRIPTION.

If the values specified for OLD- and NEW-USER/ACCOUNT/PASSWORD are the same as the values that already exist for therun control system, the RETENTION-PERIOD can be changed.

Example

Nets are planned for no longer than one day in advance. The oldpassword should therefore remain valid until 06:00 hours on thefollowing day (take the runtime of the nets into consideration):RETENTION-PERIOD=*02.06.00

U5184-J-Z125-7-76 195

CHANGE-NET-DESCRIPTION Mask AVN007

OLD-CLASS==value Job class that is to be changed in the net description.

=*INS If there is no job class in the net description, *INS must be specified.

NEW-CLASS==value New job class

=*DEL The job class in the net description will be deleted (replaced withblanks).

OLD-LOG==value Parameter value that is to be changed in the net description.

=*INS If there is no LOG value in the net description, *INS must bespecified.

NEW-LOG==value YES or NO can be specified as the new value.

=*DEL The parameter in the net description will be deleted (replaced withblanks).

OLD-CAT==value Parameter value that is to be changed in the net description.

=*INS If there is no CAT value in the net description, *INS must bespecified.

NEW-CAT==value catid or jvname can be specified as the new value.

=*DEL The parameter in the net description will be deleted (replaced withblanks).

196 U5184-J-Z125-7-76

COPY-NET-DESCRIPTION

COPY-NET-DESCRIPTIONCopy net description

The COPY-NET-DESCRIPTION statement supports copying of an individual net or subnetwithin the net library NETLIB.If a net is to be copied to a foreign NETLIB, this can be done with the COPY-ELEMENTstatement via an external file/library (see page 207).

The net to be copied is selected either directly by specifying the net name or by marking itwith S or Y in the net overview.A net for which no structure has been defined can only be copied by marking it with Y.

The COPY-NET-NAME entry is mandatory; under this name the new net is stored in the netlibrary. If the net specified under COPY-NET-NAME already exists, the net or parts of thenet will be overwritten, provided OVERWRITE=YES is specified. With OVERWRITE=NOthe net will not be copied.

If FROM-INDEX and TO-INDEX are omitted, the entire net will be copied; otherwise, onlythe subnet delimited by these two parameters is copied. The records are inserted in the netlocated under COPY-NET-NAME according to their index. If the target net already has arecord with JOB-INDEX and NAME or COND-INDEX and NAME, this record will beoverwritten.If FROM-INDEX, TO-INDEX and AFTER-INDEX are specified, it is still possible for netstructures to be created that have to be modified by means of MODIFY-NET-DESCRIPTIONbefore they can be processed.

If the net does not yet exist, the net parameters of the net to be copied will be included inthe new net.With copying, new nets are created only with the user group of the person executing thefunction. It is not possible to create nets with a foreign user group.

If a user who does not have the necessary authorization copies nets of a foreign user group,the value of the RUN-CONTROL-SYSTEM parameter is set to *STD in the net description.

Note that the names of documentation elements in a net cannot be modified. Thus, whenspecifying user groups after the copying process, modifications must be carried out bymeans of MODIFY-NET-DESCRIPTION.

U5184-J-Z125-7-76 197


NET-NAME=Name of a net whose description is to be copied.

NET-NAME=$ug_Name of a user group; causes an overview of nets belonging to the user group to bedisplayed.If no user group is specified, the user group of the person executing the function is assumedby default.

NET-NAME=netnameElement name in the NETLIB.This leads directly to the net description selection.


If the statement is issued without operands, an overview of all nets of the associated usergroup is displayed.



198 U5184-J-Z125-7-76

Mask AVN012 COPY-NET-DESCRIPTION


COPY-NET-NAME Input parameter.netnameNew name of the copied net description. The net name is prefixedwith the user group of the person executing the function.

DATE Output parameter.Date of last modification.

IND Input parameter."index" is only processed in conjunction with the S mark; it causesan overview to be displayed containing the structure elementsstarting at the specified index level.

M Input parameter.Mark column.

S (Select) The marked net description is to be copied with the selection ofparticular structure elements.

Y (Yes) The marked net description is to be copied as it stands but with anew name.

N (No) All net descriptions are to be copied, with the exception of thosemarked with an N.

NET-NAME Output parameter.$ug_netnameNames of the net descriptions presented for copying.

OVERWRITE Input parameter.

YES An existing net with the same name will be overwritten.

NO An existing net with the same name will not be overwritten.


COPIED The net description was copied.

NO-COPY The net description was not copied although it was marked. Eitherthere is no new name or the net already exists andOVERWRITE=YES was not specified.

ERROR An illegal name was specified under COPY-NET-NAME.

U5184-J-Z125-7-76 199

COPY-NET-DESCRIPTION Mask AVN005

AVN005 - Display net description for further parameter specification

AFTER-INDEX Input/output parameter.Target index.The marked structure elements are copied behind the specifiedindex.

COPY-NET-NAME Input/output parameter.Name of the net description copy.

FROM-INDEX Input/output parameter.Index level as of which the net description is to be copied.

IND Output parameter.Index level of the structure element.Depending on the FU or TYPE parameter, this is either a JOB-INDEX or a COND-INDEX. The elements to be copied are selectedvia the mark column.


Y (Yes) The marked description is to be copied.

N (D (No) All the net descriptions are to be copied, with the exception of thosemarked with an N.

Note

The mark will not be processed if the FROM-INDEX and/or TO-INDEX parameters were specified.

OVERWRITE Input/output parameter.This specifies whether or not the net description is to be overwrittenif it already exists in the net library.{YES | NO}

RESULT The copied structure elements are identified with an acknowl-edgment.COPIED

TO-INDEX Input/output parameter.Index level up to which the net description is to be copied.

The remaining parameters are output parameters and are described under the CREATE-NET-DESCRIPTION statement.

200 U5184-J-Z125-7-76

SHOW-NET-DESCRIPTION

SHOW-NET-DESCRIPTIONDisplay net description

The SHOW-NET-DESCRIPTION statement enables the user to display the net descriptionscontained in the net library NETLIB or NETSYS and to create the list of a net descriptionvia the PRINT operation. The display is obtained either by specifying a statement with aunique net name or by selecting a net from an overview. The display covers three masks,with the possibility of paging sequentially through all the information (CONTINUE).

With the SHOW-NET-DESCRIPTION statement the following types of documentation canbe displayed for the nets:

– net documentation– job documentation and– condition documentation

The current documentation element is displayed by means of the DOCUMENT operation:

Net documentationMask AVN001 (net parameters)Mask AVN004 (net structure)Mask AVN006 (net masks)Mask AVN020 (net plan data)

Job documentationMask AVN002 (job/S procedure parameters)Mask AVN009 (SV job parameters)Mask AVN021 (plan data)

Condition documentationMask AVN003 (parameters)Mask AVN008 (parameters)Mask AVN030 (parameters)Mask AVN031 (parameters)Mask AVN032 (parameters)Mask AVN022 (plan data)Mask AVN023 (plan data)Mask AVN024 (plan data)

The PRINT operation can be used to output

– a list of selected nets (no element marked in the AVN011 mask), or

– a list of individual net descriptions (corresponding nets marked in the AVN011 mask)to a SAM file (print file).

U5184-J-Z125-7-76 201


With PRINT, the AVS015 mask is presented for entering the name of the print file.

If the print file is not to be output, the RETURN operation should be entered in the AVS015mask (see PRINT operation on page 24).

NET-NAME=Name of a net whose description is to be displayed.

NET-NAME=$ug_Name of the user group.If the system user group $ugsys is specified, NETSYS is searched; otherwise NETLIB issearched. If no user group is specified, all elements of the user’s own user group aredisplayed.

NET-NAME=netnameElement name in the NETLIB or NETSYS.Depending on the value specified for the OBJECT operand, this entry leads directly to adisplay of the net description.


If no net name is entered, all elements of the specified user group are displayed.

OBJECT=Selects the net description data to be displayed. This operand is only permissible inconjunction with a fully qualified net name.

OBJECT=NETThe net parameters are to be displayed.

OBJECT=PSTThe net plan data items are to be displayed.

OBJECT=MAPThe net mask table is to be displayed.

OBJECT=STRThe overview of structure elements is to be displayed.

If OBJECT is omitted, the overview of net parameters is displayed.




202 U5184-J-Z125-7-76

Mask AVN011 SHOW-NET-DESCRIPTION

AVN011 - Overview of net descriptions

The parameters of the AVN011 mask are described under the MODIFY-NET-DESCRIPTION statement. The input or output parameter function is different here, sincethe AVN011 mask was called by means of the SHOW-NET-DESCRIPTION statement.


IND;OBJ Input parameter.This is processed only in connection with the S mark.{index | NET | PST | MAP | STR}

index The index entry causes an overview to be displayed containing thestructure elements, starting at the desired index level.

NET The AVN001 mask is displayed with the net data.

PST The AVN020 mask is displayed with the net plan data.

MAP The AVN006 mask is displayed with the table of net masks.

STR Entering STR leads to the display of an overview containing thestructure elements starting at the first index level.

If OBJECT is omitted, this causes a display of the net parameters,with the possibility of paging further through the net descriptionusing CONTINUE.

M Input parameter.

S (Select) The marked net description is to be displayed.

Y (Yes) An overview of the entire net is to be displayed. This mark isprocessed only if PRINT is specified.

It is not permitted for a mask to have different marks.

NET-NAME Output parameter.$ug_netnameNames of the net descriptions.

RESULT This parameter is irrelevant here.

U5184-J-Z125-7-76 203

SHOW-NET-DESCRIPTION Masks AVN001/...

AVN001 - Display the net parameters


AVN020 - Display the net plan data


AVN006 - Display the table of net masks

The parameters of mask AVN006 are described under the CREATE-NET-DESCRIPTIONstatement. The D, Y and N marks are prohibited here.

AVN004 - Display the net structure with the structure elements


M Input parameter.

S (Select) The marked description is to be displayed.

AVN002 - Display the parameters for structure elementswith FU=J/P and TYPE=STD/MOD/EXT/EXX


AVN003 - Display the parameters for structure elementswith FU=C and TYPE=JVA


AVN008 - Display the parameters for structure elementswith FU=C and TYPE=NET/JOB/RES/VAL


204 U5184-J-Z125-7-76

Masks AVN009/... SHOW-NET-DESCRIPTION

AVN009 - Display the parameters for structure elementswith FU=X and TYPE=STD/MOD/EXT


AVN030 - Display the parameters for structure elementswith FU=A/M/D and TYPE=RES/VAL


AVN031 - Display the parameters for structure elementswith FU=D and TYPE=NET/JOB


AVN032 - Display the parameters for structure elementswith FU=W and TYPE=TIM


AVN021 - Display the plan data for structure elementswith FU=J/P/X and TYPE=STD/MOD/EXT/EXX


AVN022 - Display the plan data for structure elementswith FU=C and TYPE=JVA/NET/JOB/RES/VAL


AVN023 - Display the plan data for structure elementswith FU=W and TYPE=TIM


AVN024 - Display the plan data for structure elementswith FU=D and TYPE=NET/JOB


U5184-J-Z125-7-76 205

DELETE-NET-DESCRIPTION

DELETE-NET-DESCRIPTIONDelete net description

The DELETE-NET-DESCRIPTION statement enables the user to delete net descriptionsfrom the net library NETLIB assigned to him via his user group. Either a single descriptioncan be deleted by specifying the statement with a unique net name, or one or more descrip-tions can be deleted by making appropriate entries in the mark column of the overviewmask.

NET-NAME=Name of a net whose description is to be deleted.

NET-NAME=$ug_Name of the user group.If no user group is specified, all element of the user’s own user group are displayed.

NET-NAME=netnameElement name in the NETLIB.This entry directly causes the net description to be displayed in the overview.

If the net name is entered via a partial qualification (final character *), an overview isdisplayed of those elements whose names begin with the partial qualification.If no net name is entered, all elements of the specified user group are displayed.

If the statement is issued with no operands specified, this causes an overview to bedisplayed containing all nets belonging to the associated user group.

Note

Net descriptions in the NETSYS net library can only be deleted by the AVAS adminis-trator (see "AVAS for the Administrator" [3]).

DELETE-NET-DESCRIPTION


206 U5184-J-Z125-7-76

Mask AVN011 DELETE-NET-DESCRIPTION

AVN011 - Overview of net descriptions

The parameters for the AVN011 mask are described under the MODIFY-NET-DESCRIPTION statement. The parameter IND;OBJ is irrelevant here, since the AVN011mask was called by the DELETE-NET-DESCRIPTION statement.

M Input parameter.

Y (Yes) The marked net description is to be deleted. The S and N marks areprohibited here.

NET-NAME Output parameter.$ug_netnameNames of the net descriptions presented for deletion.


DELETED The element was deleted from the NETLIB.

LOCKED The element is currently locked.

U5184-J-Z125-7-76 207

COPY-ELEMENT

3.6 COPY-ELEMENTCopy library elements from/to external file or library

The COPY-ELEMENT statement can be used to copy elements from an external SAM fileor PLAM library to an AVAS library, or elements from an AVAS library to individual externalSAM files or to a PLAM library.

The following AVAS libraries can be processed:

NETLIB (net descriptions)

JCLLIB (jobs, S procedures, SV jobs and JCL elements)

DOCLIB (documentation elements)

CALLIB (AVAS calendar)

The processing mode is selected by means of the MODE operand. It is not possible to enteror modify this operand in the parameter fields within the mask.

AVAS outputs to external libraries have no user group. Conversely, the input libraries mustnot contain user groups. AVAS does not check the element names.

MODE=LIBOUTOutput from an AVAS library to an external PLAM library. The selected elements are copiedto the external library with their element names unchanged.

Operands Parameters Number ofelementsprocessed

MODE USER-GROUP EXTERNAL-FILE ELEMENT/GROUP

LIBOUT - libname element n

LIBIN [$ug] libname " n

SAMOUT - prefix " n

SAMIN - samfile [$ug_]element 1

COPY-ELEMENT

MODE=LIBOUT | LIBIN [,USER-GROUP=$ug] | SAMOUT | SAMIN

208 U5184-J-Z125-7-76

COPY-ELEMENT

MODE=LIBINRead from an external PLAM library to an AVAS library. Privileged users may use theUSER-GROUP operand to specify which user group is to be employed as a name prefixwhen the selected elements are entered in the AVAS library.If USER-GROUP is omitted, the user group of the person executing the function is assumedby default.

Notes

– Wildcards cannot be specified for selecting elements in the external library.

– If the external file is a library, the elements are either sought in section J of the JCLLIBand section S of the NETLIB, DOCLIB and CALLIB or output to the correspondingsections.

– AVAS elements cannot be renamed outside of AVAS. COPY-NET-DESCRIPTION canbe used to create a copy with a freely selectable name. Specifying COPY-ELEMENTMODE=LIBOUT | SAMOUT causes the copy to be transferred to another AVAS system,where it is read into an AVAS library by means of COPY-ELEMENT MODE=LIBIN |SAMIN.

MODE=SAMOUTOutputs selected elements from an AVAS library to individual external SAM files.Each SAM file name is composed of an optional prefix and the element name without auser group.

MODE=SAMINReads the element from an external SAM file to an AVAS library.The element name is specified in the ELEMENT/GROUP parameter.

Privileged users may enter the element under a foreign user group.

Notes

– If an SV job or an S procedure is to be copied with MODE=LIBIN | SAMIN and AVAS-USER-LIBRARY=JCLLIB, the separator string assigned to the function (FU=X orFU=P) must be used in the element. This separator string is defined by the AVASadministrator using the generation parameters. If parameters are being used, therelevant separator string must be present as a record in the element, between theprocedure part (job part) and the procedure parameters (job parameters). If no param-eters are present, the separator string must be stored as the last record in the element.

If the element does not contain a separator string, it is interpreted as a job (FU=J), andis entered as such in the JCLLIB directory.

U5184-J-Z125-7-76 209

COPY-ELEMENT

If a separator string is recognized during copying, the element will be recorded in theJCLLIB directory as an S procedure or an SV job, depending on the separator string.All the records in the element which are read in after the separator string are interpretedby AVAS as records containing parameters.

– In the case of a COPY-ELEMENT with MODE=LIBIN | SAMIN, the following rules applyto the overwriting of elements:

– an element with the same name and type can be overwritten

– an element of type JOB can be overwritten with an S procedure

– a job or an S procedure cannot be overwritten with an SV job

– an SV job cannot be overwritten with an S procedure.

Any attempt to overwrite an S procedure or an SV job with a job of the same name isimpermissible, and is rejected with an appropriate error message.

– In the case of a COPY-ELEMENT with MODE=LIBOUT | SAMOUT, AVAS does nothave the necessary information.Correspondingly, if OVERWRITE=YES is specified, the overwriting will be carried outwith no checks.

– If a user copies a net with MODE=LIBIN | SAMIN and changes the net’s user group, thevalue of the RUN-CONTROL-SYSTEM parameter is set to *STD in the net descriptionif the user does not have the appropriate authorization.

USER-GROUP=$ugUser group under which the elements are to be entered in the AVAS library.This operand is only permitted in conjunction with MODE=LIBIN.

210 U5184-J-Z125-7-76

Mask AVS011 COPY-ELEMENT

AVS011 - Input/output of AVAS library elements

AVAS-USER-LIBRARYInput/output parameter.Abbreviated name of the AVAS library to be processed:NETLIB, JCLLIB, DOCLIB or CALLIB.


ELEMENT/GROUP Input parameter.Selects the elements to be processed, with regard to the inputlibrary.

element Element name.

AVAS-USER-LIB=NETLIB: [$ug_]netname =JCLLIB: [$ug_]jobname =DOCLIB: [$ug_]elementname =CALLIB: calendar

$ug_ User group.

AVAS-USER-LIB=NETLIB: $ug_ =JCLLIB: $ug_ =DOCLIB: $ug_

Exception

MODE=SAMIN is used to specify what the element in the AVAS-USER-LIBRARY is to be called.

ELEMENT-NAME Output parameter.List of fully qualified element names presented for selection byspecifying ELEMENT/GROUP, relative to the AVAS-USER-LIBRARY.

AVAS-USER-LIBRARY=NETLIB: $ug_netname =JCLLIB: $ug_jobname =DOCLIB: $ug_elementname =CALLIB: calendar

MODE=LIBIN: The user group of the elements is identical to the USER-GROUPspecification.

MODE=SAMIN:Same contents as ELEMENT/GROUP.

U5184-J-Z125-7-76 211

COPY-ELEMENT Mask AVS011

EXTERNAL-FILE Input/output parameter.{libname | prefix | samfile}

libname External PLAM library from which the elements are to be read or towhich the elements are to be written.

prefix Prefix with which the element is to be output to the SAM file.

samfile Name of the SAM file. The SAM file contains an element.


Y (Yes) The element is to be copied.

N (No) The element is not to be copied. All elements not marked with N willbe copied.

MODE Output parameter(see description of the MODE operand).

OVERWRITE Input/output parameter.{YES | NO}The element is (YES) or is not (NO) to be overwritten.


COPIED The element was copied.

OVERWRITE The element was copied and an existing element was overwritten.

NO-COPY The element could not be copied.

WARNING The element has been copied. CHECK discovered errors in theelement. A report has been produced.

ERROR The element has not been copied. An error occurred or CHECKdiscovered serious errors in the element.

Note

With COPY-ELEMENT MODE=SAMOUT the length of the optionally specified prefixmust be chosen such that, together with the AVAS element name, the maximumpermitted total length for BS2000 file names is not exceeded.When the full name length allowed for documents (43 characters) is used up, thendepending on the length of the catalog ID and user ID, only a single-character prefixmay be possible.


U5184-J-Z125-7-76 213

4 Condition descriptionsThe following statements can be used for editing condition descriptions of the types NET,JOB, RESOURCE and VALUE. No condition descriptions are created for conditions of typeJVA.


ADD-COND-DESCRIPTIONAdd condition description

The ADD-COND-DESCRIPTION statement is used to define condition descriptions of thetypes RES and VAL, and save them in the run control file. Condition descriptions of typesRES and VAL can also be created by nets which are being executed.

Condition descriptions of types NET and JOB are created by AVAS in the case of thefunctions SUBMIT-NET and REPEAT-NET, but they cannot be defined using ADD-COND-DESCRIPTION.

Mask AVD030 is displayed, to enable all the necessary entries to be made. It is not possibleto swap to another mask (the OBJECT operand is not permitted here).

Input fields into which no value is put will be given the default values.

A condition description is saved by performing the SAVE operation.After a condition description has been saved with SAVE, it can then only be modified in adialog by using the MODIFY-COND-DESCRIPTION statement.

When ADD-COND-DESCRIPTION is used, no journal record is output.

ADD-COND-DESCRIPTION Add a condition description

MODIFY-COND-DESCRIPTION Modify a condition description

DELETE-COND-DESCRIPTION Delete a condition description

SHOW-COND-DESCRIPTION Display a condition description

214 U5184-J-Z125-7-76

ADD-COND-DESCRIPTION Dialog functions for condition descriptions

COND-NAME=Name of the condition description

COND-NAME=$ug_Name of the user group

If no user group is specified, the condition description is supplemented internally by the usergroup of the user exercising the function.

COND-NAME=condnameName of the condition description, which must be unique within the user group. From 1-24characters are permitted.

TYPE=Type of the condition descriptionThe type of the condition must be specified when the statement is called. The input param-eters depend on the type and thus, after it is selected, the type cannot be changed withinthe dialog.

TYPE=RESA condition description with the type RESOURCE is to be created.

TYPE=VALA condition description with the type VALUE is to be created.

ADD-COND-DESCRIPTION

COND-NAME=[$ug_ ]condname

[,TYPE=RES | VAL]

U5184-J-Z125-7-76 215

ADD-COND-DESCRIPTION Mask AVD030

AVD030 - Specification of a condition description

COND-DOC Input/output parameter.Create user documentation.{*STD | element | *NONE}

*STD The documentation is created or sought in the DOCLIB under thedefault name $ug_condname.

element Element name for the documentation in the DOCLIB or DOCSYS:$ug_docname$ugsys_docnamedocname

*NONE No documentation is saved for the condition description.

COND-NAME Output parameter.Name of the condition description, as defined in the operand.

COND-STATUS Output parameter.Status of the condition descriptionFor the ADD-COND-DESCRIPTION statement, this field is initiallyempty. The status is given a value when the SAVE operation isperformed.

For COND-TYPE=RESStatus of the COND-VALUE specified in this mask.

For COND-TYPE=VALStatus CREATED

COND-TEXT Input/output parameter.Brief text, not exceeding 120 characters, describing the condition.

COND-TYPE Output parameter.The condition type, as given by the TYPE operand{RES | VAL}

216 U5184-J-Z125-7-76

Mask AVD030 ADD-COND-DESCRIPTION

COND-VALUE Input/output parameter.Status of the condition.

For COND-TYPE=RESStatus of the condition

For COND-TYPE=VALValue of the condition

CREATED BY Output parameter.ID of the user who created the entry.avas-user-id

CREATION-DATE Output parameter.Date when the condition description was created; this correspondsto the current date at the time of the SAVE, in the formdd.mm.yy hh:mm:ss

INDEX This parameter has no meaning here, and is locked against input.

LAST-UPDATE This parameter has no meaning here, and is locked against input.

LIFE-TIME This parameter has no meaning here, and is locked against input.

VALUE-FORMAT Input/output parameter.Selects the display format for COND-VALUEThis parameter is only evaluated for COND-TYPE=VAL.

CHAR The value COND-VALUE is output in alphanumeric form.

HEXA The value COND-VALUE is output in hexadecimal form.

CREATED A description has been created; the resource is notyet available.

FREE The resource is freely available.

SHARE The resource is shareable and is currently in use.

EXCLUSIVE The resource is being used exclusively.

ERROR The resource is subject to an error.

string Depending on the VALUE-FORMAT parameter, thevalue is displayed in alphanumeric (c-string) orhexadecimal (x-string) format.

U5184-J-Z125-7-76 217

Dialog functions for condition descriptions MODIFY-COND-DESCRIPTION

MODIFY-COND-DESCRIPTIONModify condition description

The MODIFY-COND-DESCRIPTION statement allows existing condition descriptions of thetypes NET, JOB, RES and VAL to be amended.

Condition descriptions of these types can also be modified (and deleted) by nets which arebeing executed.

The condition description which is to be modified will be directly displayed by the maskAVD030 if the required condition description can be uniquely selected using the prescribedoperand values. This requires at least the fully-qualified COND-NAME and, if this is notunique, the TYPE operand in addition.For condition descriptions with COND-TYPE=NET or JOB, when there is multiple useunique identification is only possible via CREATED BY and NET-NAME or INDEX. In thiscase, specifying the operands COND-NAME and TYPE is also inadequate for anunambiguous selection to be made. If the system cannot make an unambiguous identifi-cation, then the condition descriptions selected by applying the specified operand valueswill be presented to the user in the overview mask AVD040.

The selection of condition descriptions can be further restricted by specifying the STATUSoperand.The STATUS operand is not displayed in the individual processing (masks AVD030 andAVD031) and can also not be specified there. Any attempt to specify it will be rejected witha message. The condition status displayed in masks AVD030/AVD031 can differ from thevalue defined in the STATUS operand if the status is modified (by the run control system orthrough statements) between the time the conditions are selected via the predefinedoperands and the time of the individual display (masks AVD030/AVD031).The status value defined via the STATUS operand is not checked for legitimacy with regardto a TYPE operand which may have been predefined.

Condition descriptions can be selected in mask AVD040 (S mark); EXECUTE causes theseto be displayed individually in mask AVD030 (depending on OBJECT). It is unnecessary tospecify the OBJECT operand (default).

By entering the operand OBJECT=USR, or by using the CONTINUE operation, it is possibleto swap from mask AVD030 to a display of the condition testing nets in the conditiondescription (AVD031).

Modifications to a condition description (AVD030) become effective when SAVE isperformed. The deletion of a condition testing net from a condition description (AVD031) iseffected by an EXECUTE statement.

218 U5184-J-Z125-7-76

MODIFY-COND-DESCRIPTION Dialog functions for condition descriptions

When MODIFY-COND-DESCRIPTION is used, no journal record is output.

COND-NAME=Name of the condition description, the values in which are to be modified.


If no user group is specified, the condition descriptions for the own user group will be output.

COND-NAME=condnameName of the condition description; from 1-24 characters are permitted.

If the condition description is specified in partially qualified form (last character *), the resultwill be an overview of the existing entries which have names beginning with the partial quali-fication.

If condname is not specified, all the descriptions for the specified user group will be output.

If the COND-NAME operand is not specified, all the descriptions for the own user group willbe output.

TYPE=Type of the condition descriptionIt is helpful to specify the type of the condition to limit the number of descriptions displayedfor a partially qualified condition name.

TYPE=NETCondition descriptions of the type NET should be displayed.

TYPE=JOBCondition descriptions of the type JOB should be displayed.

TYPE=RESCondition descriptions of the type RES (resource) should be displayed.

TYPE=VALCondition descriptions of the type VAL should be displayed.

MODIFY-COND-DESCRIPTION

[COND-NAME=[$ug_ ]condname]

[,TYPE=NET | JOB | RES | VAL]

,OBJECT=DES | USR]

[,STATUS=ABENDED | CREATED | DELETED | ENDED | ERROR | EXCLUSIVE | FREE | IGNORED |

NO-PLAN | NO-SUBMIT | SHARE | SKIPPED]

U5184-J-Z125-7-76 219

Dialog functions for condition descriptions MODIFY-COND-DESCRIPTION

OBJECT=Selects the mask to be used in modifying the condition descriptions.For overview processing (display of mask AVD040), the specified value is copied into themask parameter OBJ.

OBJECT=DESMask AVD030, for modifying the values in the condition descriptions, is presented.

OBJECT=USRMask AVD031, in which the users of the condition descriptions can be displayed anddeleted, is presented.

STATUS=Status of the condition descriptions to be displayed.The status which a condition description may take on depends on the type of the condition.

STATUS=ABENDEDDELAY-SOLUTION=CANCEL or CANCEL-NET

STATUS=CREATEDA description has been created.

STATUS=DELETEDThe task was deleted with the D mark in MODIFY-SUBMIT-NET.

STATUS=ENDEDNet/job processing has ended.

STATUS=ERRORAn error has occurred.

STATUS=EXCLUSIVEThe resource is being used exclusively.

STATUS=FREEThe resource is freely available.

STATUS=IGNOREDDELAY-SOLUTION=IGNORE

STATUS=NO-PLANThe task has not been planned (SYMDAT or D mark with CREATE-PLAN-NET).

STATUS=NO-SUBMITThe task was deleted with mark D in SUBMIT-NET or REPEAT-NET.

STATUS=SHAREThe shareable resource is currently in use.

STATUS=SKIPPEDThe task was skipped during restart (RESTART-NET).

220 U5184-J-Z125-7-76

Mask AVD040 MODIFY-COND-DESCRIPTION

AVD040 - Overview of the condition descriptions

COND-NAME Output parameter.Name of the condition description.$ug_condname

COND-STATUS Output parameter.Status of the condition description.The status which a condition description may take on depends onthe type of the condition.

ABENDED DELAY-SOLUTION=CANCEL, or CANCEL-NET dialog

CREATED A description has been created.

DELETED D mark in MODIFY-SUBMIT-NET

ENDED End

ERROR Error


IGNORED DELAY-SOLUTION=IGNORE

NO-PLAN The job has not been planned (SYMDAT or D mark in CREATE-PLAN-NET).

NO-SUBMIT D mark in SUBMIT-NET or REPEAT-NET

SKIPPED Skipped during a restart (RESTART-NET)



CREATED BY NET-NAME / USEROutput parameter.Name of the net, or ID of the user, which created the description.

IND Output parameter.Index of the structure element, if the description was created via anet.

M Input/output parameter.Mark column

S (Select) Selects the condition description which is to be displayed ormodified by applying additional parameters.The appropriate mask, which depends on the OBJECT operand, isdisplayed by performing the EXECUTE operation.

U5184-J-Z125-7-76 221

MODIFY-COND-DESCRIPTION Mask AVD040

OBJ Input/output parameter.Specifies the mask for which the parameters are to be displayed ormodified.The preset value of this parameter is DES.

DES Mask AVD030, for modifying the values of the condition descrip-tions, is presented.

USR Mask AVD031, in which the users of the condition descriptions canbe displayed and deleted, is presented.


UPDATED The condition description has been modified.

NO-UPDATE The condition description has not been modified.

ERROR An error occurred during the modification.

LOCKED The condition description is locked as it is being edited by otherusers.

NOT-FOUND The condition description has now been deleted by another user ornet.

TYPE Output parameter.Condition type{NET | JOB | RES | VAL}

NET Net

JOB Job

RES Resource

VAL Defined value

222 U5184-J-Z125-7-76


AVD030 - Display a condition description to be modified

The parameters of the mask AVD030 are described under the ADD-COND-DESCRIPTIONstatement. The MODIFY-COND-DESCRIPTION statement permits the additional conditiontypes NET and JOB, so that a few additions to the meanings of the parameters arenecessary.

Modifications made in the mask are saved by using the SAVE operation.

COND-STATUS Output parameter.Status of the condition descriptionThe status which a condition description may take on depends onthe type of the condition.

ABENDED DELAY-SOLUTION=CANCEL or CANCEL-NET dialog



ENDED End

ERROR Error








COND-TYPE Output parameter.Condition type as specified by the TYPE operand{NET | JOB | RES | VAL}

COND-VALUE Input/output parameter.

For COND-TYPE=NETStatus of the net


ENDED Net processing has ended.

ABENDED DELAY-SOLUTION=CANCEL or CANCEL-NET


U5184-J-Z125-7-76 223


For COND-TYPE=JOBStatus of the job

For COND-TYPE=RESStatus of the condition

Note

The inputs SHARE and EXCLUSIVE cause the resource to beoccupied by the user.You cannot release a resource by modifying COND-VALUE.You can only release a resource by deleting the entry via maskAVD031.

Resources with the status ERROR or CREATED cannot beallocated. Any attempt to do so will be rejected with a message.

For COND-TYPE=VAL


NO-PLAN The job has not been planned (SYMDAT or D markin CREATE-PLAN-NET).




ENDED Job terminated.

ERROR Error or CANCEL-NET with CAN-TYPE=SOFT


ABENDED CANCEL-NET with CANCEL-TYPE=HARD






string Value of the conditionDepending on the parameter VALUE-FORMAT, thevalue is displayed in alphanumeric (c-string) orhexadecimal (x-string) format.

224 U5184-J-Z125-7-76

Masks AVD030/AVD031 MODIFY-COND-DESCRIPTION

CREATED BY Output parameter.Name of the net, or ID of the user, which created the description.{$ug_netname | avas-user-id}

CREATION-DATE Output parameter.Date when the condition description was created, in the formdd.mm.yy hh:mm:ss

INDEX Output parameter.Index of the structure elementOnly output if the description was created via a net.

LAST-UPDATE Output parameter.Date of the last modification to the condition description, in the formdd.mm.yy hh:mm:ss

LIFE-TIME Input/output parameter.Life of the condition description(only in conjunction with TYPE=NET and TYPE=JOB)The real time (date and hour) up to which the condition descriptionis to remain valid.Format: dd.mm.yy hh:mm:ss

VALUE-FORMAT Input/output parameter.Selects the display and input format for COND-VALUE.

CHAR The value COND-VALUE is output in alphanumeric form.

HEXA The value COND-VALUE is output in hexadecimal form.HEXA is only permitted if COND-TYPE=VAL.

AVD031 - Display the users of a condition description

Mask AVD031 displays the condition tests of nets which make reference to the specifiedcondition description.

They can be deleted using the D mark and the EXECUTE operation.

COND-NAME Output parameter.Name of the condition description$ug_condname

COND-STATUS Output parameter.Status of the condition descriptionThe status which a condition description may take on depends onthe type of the condition.

ABENDED DELAY-SOLUTION=CANCEL or CANCEL-NET dialog


U5184-J-Z125-7-76 225



ENDED End

ERROR Error








COND-TYPE Output parameter.Condition type{NET | JOB | RES | VAL}

NET Net

JOB Job

RES Resource

VAL Defined value


CREATED BY INDEX Output parameter.Index of the structure elementOnly output if the description was created via a net.

INDEX Index in the net, showing where the condition is used in the formspecified by OCCURE-VALUE.


D (Delete) The marked condition description for a net is to be deleted.The deletion takes effect when the EXECUTE operation isperformed.

226 U5184-J-Z125-7-76


NET-NAME Output parameter.Name of the net which is waiting for the condition to be satisfied, orwhich is using the resource.$ug_netname

OCCURE-VALUE Output parameter.Value of the condition, as recorded in the net at the appropriateindex point with FU=C (wait for a condition).{status | status,status,... | (OP,pos,value) |(OP,pos,value),(OP,pos,value),...}

For COND-TYPE=VALValue(s) of the condition, linked with operators.(OP,pos,value)

OP – comparison operation

If no comparison operation is specified, OP=EQ is assumed. Theparameter and the comma are then omitted (pos,value).

pos – start position for the value specification

If no value is specified for pos, pos=1 is assumed.Comparison values with neither OP nor pos are specified directly(value).If a comparison operation is specified with no start position, thecorresponding comma must nevertheless appear (OP,,value).

value – comparison value

Current value of the condition description in the run control file. Therange extends to 128 bytes.

= / EQ - equal to

< / LT - less than

> / GT - greater than

Î / LE - less than or equal to

Ï / GE - greater than or equal to

î / NE - not equal to

nnn

ć-string´

Cć-string´

X´x-string´

U5184-J-Z125-7-76 227


),( – logical OR operation

Where there are a number of condition tests, these are specified inparentheses, which links them by an OR operation.

For COND-TYPE=RES

Status or status list

For COND-TYPE=NET


For COND-TYPE=JOB


WAITING/USING Output parameter.In the case of NET, JOB and VAL conditions, function C is alwaysused to wait for a status or value. For a RES condition, the use of aresource can be specified.

WAITING The net waits for the status or value specified under OCCURE-VALUE.

USING The net is using the resource in either SHARE or EXCLUSIVEmode (only for COND-TYPE=RES).



ENDED Terminated







ENDED Terminated




228 U5184-J-Z125-7-76

DELETE-COND-DESCRIPTION Dialog functions for condition descriptions

DELETE-COND-DESCRIPTIONDelete condition description

The DELETE-COND-DESCRIPTION statement deletes condition descriptions.

Condition descriptions can also be deleted by nets which are running or by the end of theLIFE-TIME being reached.

A prerequisite for a condition description being deleted is that no net is waiting for thecondition to be satisfied. If this is doubtful, one of the statements SHOW- or MODIFY-COND-DESCRIPTION should be used to call up mask AVD031. In the event of an error,these condition descriptions in the net can be deleted.

After all the necessary entries have been made, the condition description to be deleted isdisplayed in mask AVD040.It is not permissible to swap masks to obtain an individual display or a display of the netsusing the condition. This can be done beforehand, using either the MODIFY- or SHOW-COND-DESCRIPTION statement.

If no operand is specified with the call, or only a partially qualified one, mask AVD040 willpresent all the condition descriptions which correspond to the partial qualification.For condition descriptions with COND-TYPE=NET or JOB, when there is multiple useunique identification is only possible via CREATED BY and NET-NAME or INDEX. In thiscase, specifying the operands COND-NAME and TYPE is still not enough to ensure anunambiguous selection. The selection of condition descriptions can be further restricted byspecifying the STATUS operand.The status value defined via the STATUS operand is not checked for legitimacy with regardto the TYPE operand which may have been predefined.

If the system cannot make an unambiguous identification, then the condition descriptionsselected by applying the specified operand values will be presented to the user in theoverview mask AVD040.The entries to be deleted should then be selected by marking with a Y.

The deletion of condition descriptions takes effect when the EXECUTE operation isperformed.

When DELETE-COND-DESCRIPTION is used, no journal record is output.

DELETE-COND-DESCRIPTION





U5184-J-Z125-7-76 229

Dialog functions for condition descriptions DELETE-COND-DESCRIPTION

COND-NAME=Name of the condition description which is to be deleted.




If the condition description is specified in partially qualified form (last character *), the resultwill be an overview of the existing entries which have names beginning with the partial quali-fication.

If condname is not specified, all the descriptions for the specified user group will be output.


TYPE=Type of the condition descriptionIt is helpful to specify the type of the condition to limit the number of descriptions displayedfor a partially qualified condition name, or if a fully qualified condition name is not unique.




TYPE=VALCondition descriptions of the type VAL should be displayed.

STATUS=Status of the condition descriptions to be displayed.Only the condition descriptions with the specified status are displayed.The status which a condition description may assume depends on the type of the condition.

The permissible status values are described under the MODIFY-COND-DESCRIPTIONstatement.

230 U5184-J-Z125-7-76

Mask AVD040 DELETE-COND-DESCRIPTION


The parameters of the AVD040 mask are described under the MODIFY-COND-DESCRIPTION statement.Only parameters which have a different meaning are described here.


Y (Yes) The selected condition description is to be deleted.The deletion takes effect when the EXECUTE operation isperformed.A condition description can only be deleted if it does not record anynet as being a user. If necessary, the users must first be deleted,using the MODIFY-COND-DESCRIPTION statement.


DELETED The condition description has been deleted.

LOCKED The condition description is locked as it is being edited by otherusers.

NO-DELETE The condition description has not been deleted, because there arestill nets waiting for events from the condition description.

NOT-FOUND The condition description has already been deleted by another useror net.

U5184-J-Z125-7-76 231

Dialog functions for condition descriptions SHOW-COND-DESCRIPTION

SHOW-COND-DESCRIPTIONDisplay condition description

Using the SHOW-COND-DESCRIPTION statement, existing condition descriptions of typeNET, JOB, RES and VAL can be displayed.

It is not necessary to specify the operand OBJECT=DES in order to display mask AVD030(default).

Mask AVD031, which displays all the nets which use the condition description, is called upby entering the operand OBJECT=USR.

If no operand is specified with the call, or only a partially qualified one, mask AVD040 willbe presented, from which a condition description can then be selected.For condition descriptions with COND-TYPE=NET or JOB, when there is multiple useunique identification is only possible via CREATED BY and NET-NAME or INDEX. In thiscase, specifying the operands COND-NAME and TYPE is also inadequate for anunambiguous selection to be made. If the system cannot make an unambiguous identifi-cation, then the condition descriptions selected by applying the specified operand valueswill be presented to the user in the overview mask AVD040.

The selection of condition descriptions can be further restricted by specifying the STATUSoperand.The STATUS operand is not displayed in the individual processing (masks AVD030 andAVD031) and can also not be specified there. Any attempt to specify it will be rejected witha message. The condition status displayed in masks AVD030/AVD031 can differ from thevalue defined in the STATUS operand if the status is modified (by the run control system orthrough statements) between the time the conditions are selected via the predefinedoperands and the time of the individual display (masks AVD030/AVD031).The status value defined via the STATUS operand is not checked for legitimacy with regardto the TYPE operand which may have been predefined.

COND-NAME=Name of the condition description, the values in which are to be displayed.

SHOW-COND-DESCRIPTION



[,OBJECT=DES | USR]



232 U5184-J-Z125-7-76

SHOW-COND-DESCRIPTION Dialog functions for condition descriptions



STATUS=Status of the condition descriptions to be displayed.Only the condition descriptions with the specified status are displayed.The status which a condition description may assume depends on the type of the condition.

The permissible status values are described under the MODIFY-COND-DESCRIPTIONstatement.


If the condition description is specified in partially qualified form (last character *), the resultwill be an overview of the existing entries which have names beginning with the partial quali-fication.If condname is not specified, all the descriptions for the specified user group will be output.


TYPE=Type of the condition descriptionIt is helpful to specify the type of the condition to limit the number of descriptions displayedfor a partially qualified condition name.




TYPE=VALCondition descriptions of the type VAL (corresponding to JVA) should be displayed.

OBJECT=Selects the mask to be used in modifying the condition descriptions.For overview processing (display of mask AVD040), the specified value is copied into themask parameter OBJ.

OBJECT=DESMask AVD030, containing the values in the condition descriptions, is presented (default).

OBJECT=USRMask AVD031, in which the users of the condition descriptions are displayed, is presented.

U5184-J-Z125-7-76 233

SHOW-COND-DESCRIPTION Masks AVD040/AVD030


The parameters of the AVD040 mask are described under the MODIFY-COND-DESCRIPTION statement.Only parameters which have a different meaning are described here.


S (Select) Selects the condition description, which can only be displayed byapplying additional parameters.The appropriate mask, which depends on the OBJ operand, isdisplayed by performing the EXECUTE operation.


NOT-FOUND The condition description has already been deleted by another useror net.

AVD030 - Display of a condition description

The parameters of the AVD030 mask are described under the ADD-COND-DESCRIPTIONstatement. The SHOW-COND-DESCRIPTION statement permits the additional conditiontypes NET and JOB, so that a few additions to the meanings of the parameters arenecessary.All the parameter fields are output parameters.

COND-STATUS Output parameter.Status of the condition description.The status which a condition description may take on depends onthe type of the condition.




ENDED Net/job processing has ended.

ERROR An error has occurred.




234 U5184-J-Z125-7-76

Mask AVD030 SHOW-COND-DESCRIPTION


SKIPPED The task was skipped during a restart (RESTART-NET)



COND-TYPE Output parameter.Condition type as specified by the TYPE operand{NET | JOB | RES | VAL}

COND-VALUE Output parameter.

For COND-TYPE=NET: status of the net

For COND-TYPE=JOB: status of the job

For COND-TYPE=RES: status of the condition


ENDED Net processing has ended.








ENDED Job terminated.









U5184-J-Z125-7-76 235

SHOW-COND-DESCRIPTION Mask AVD030/AVD031

For COND-TYPE=VAL


CREATION-DATE Output parameter.Date when the condition description was created, in the formdd.mm.yy hh:mm:ss

INDEX Output parameter.Index of the structure elementOnly output if the description was created via a net.

LAST-UPDATE Output parameter.Date of the last modification to the condition description, in the formdd.mm.yy hh:mm:ss

LIFE-TIME Output parameter.Lifetime of the condition descriptionThe real time (date and hour) up to which the condition descriptionis to remain valid.Format: dd.mm.yy hh:mm:ss

AVD031 - Display the users of a condition description

The parameters of the AVD031 mask are described under the MODIFY-COND-DESCRIPTION statement.

Since mask AVD031 is called up by the SHOW-COND-DESCRIPTION statement, the Dmark cannot be used here to delete condition descriptions.

string Value of the conditionDepending on the parameter VALUE-FORMAT, thevalue is displayed in alphanumeric (c-string) orhexadecimal (x-string) format.


U5184-J-Z125-7-76 237

5 CalendarsIn order to perform time scheduling via a calendar, each user group must have a calendarsupplied with current dates. The name of the calendar is preset for each user group bymeans of the system parameters.


CREATE-CALENDAR Set up a new calendar

MODIFY-CALENDAR Modify a calendar

SHOW-CALENDAR Display a calendar

COPY-CALENDAR Copy a calendar with its symdats

DELETE-CALENDAR Delete a calendar

238 U5184-J-Z125-7-76

CREATE-CALENDAR

CREATE-CALENDARSet up new calendar

The CREATE-CALENDAR statement sets up a new calendar in the calendar library.

The privileged user can set up new calendars with any names and enter calendar dates inthem.The normal user can enter his dates only in the calendar assigned to his user group.

Data required for the calendar includes its start and end dates and the production-free daysthat fall within this range.The user can define which days of the week are to be generated as planned as production-free days.

In the case of symbolic start dates, a distinction is made between the start dates defined bythe user with MODIFY-CALENDAR (USER symbolic date) and the start dates generatedusing CREATE-CALENDAR (SYSTEM symbolic date).When the calendar is set up, the days of the week are generated as symbolic dates.

The SYMDAT-NAME parameter (AVC001 mask) can be used to control whether and withwhich additional SYSTEM symbolic dates the calendar is to be generated.The names of the SYSTEM symbolic dates can be defined in the AVC001 mask.The user cannot modify the SYSTEM symbolic dates generated for the calendar.

USER symbolic dates are not processed with this statement. These can be defined andedited using the MODIFY-CALENDAR statement.

The calendar integrated in AVAS covers up to 31.12.2080.A newly set up calendar cannot be processed using AVAS V3.0A.

CALENDAR-NAME=calendarName of a calendar to be entered in the calendar library.This causes the AVC001 mask to be displayed.No operand has to be specified to set up a calendar assigned to the user via the systemparameters.

CREATE-CALENDAR

CALENDAR-NAME=calendar

U5184-J-Z125-7-76 239

CREATE-CALENDAR Mask AVC001

AVC001 - Set up a calendar

CALENDAR-NAME Output parameter.Name of the calendar to be set up.

FIRST-CALENDAR-DATEInput/output parameter.First day in the calendar (dd.mm.yy).

If the calendar is to be created using SYMDAT-NAME=*STD/*ALL,the calendar must begin with the first day of the month.

LAST-CALENDAR-DATEInput/output parameter.Last day in the calendar (dd.mm.yy).

If the calendar is to be created using SYMDAT-NAME=*STD/*ALL,the calendar must end with the last day of the month.

Note

The calendar cannot cover more than three years (interval betweenFIRST-CALENDAR-DATE and LAST-CALENDAR-DATE).

SYMDAT-NAME Input/output parameterThe parameter can be used to define which SYSTEM symbolicdates are to be generated when the calendar is set up.{*NONE | *STD | *ALL}

*NONE AVAS does not add any additional SYSTEM symbolic dates to thecalendar days when the calendar is set up.

*STD AVAS generates the following SYSTEM symbolic dates and addsthem to the calendar days:

The user can define the names of the SYSTEM symbolic dates inthe AVC001 mask. Otherwise, the default names that appear inbrackets ( ) are used.

Symbolic date for every day (TGL)

Symbolic date for working day (WT)

Current day of the month (K)

Current working day of the month (A)

Last working day of the month (ULTIMO)

240 U5184-J-Z125-7-76

Mask AVC001 CREATE-CALENDAR

*ALL The names of the following SYSTEM symbolic dates, derived fromthe defined default names, are generated for the SYSTEM symbolicdates described under *STD:

In addition, the following SYSTEM symbolic dates, together with thecorresponding names, are generated for all the days of the week(MON, TUE, WED, THU, FRI, SAT and SUN):

Example for Monday (MON)

Note

Only days with TYPE=WORK are interpreted as working days.The names of the SYSTEM symbolic dates defined or formed forCREATE-CALENDAR are preceded by an asterisk (*) when thesymbolic date is stored on the calendar day.

In the net, the symbolic date must be entered without the *.

nnth working day of the month mm (AnnMmm)

nnth day of the month (KnnMmm)

nnth day of the month, which is also a working day (KnnWT)

nnth day of the month, which should also be a working dayIf this day is not a working day, the symbolic date isentered for the previous working day.

(KnnVWT)

nnth. day of the month, which should also be a working dayIf this day is not a working day, the symdat is entered for thenext working day.

(KnnNWT)

Last working day in the month (ULTIMO)

Last working day in the month mm (ULTIMOmm)

n working days before the last working day of the month(n = 1 ... 5)

(ULTIMOMn)

Monday, which is a working day (WTMON)

Monday, which should also be a working dayIf this day is not a working day, the symbolic date is enteredfor the previous working day.

(WTVMON)

Monday, which should also be a working dayIf this day is not a working day, the symbolic date is enteredfor the next working day.

(WTNMON)

nth Monday of m in this month (MONnm)

U5184-J-Z125-7-76 241


Examples

Input mask: AVC001 Field: DAY OF THE MONTH = EVDM

TYPE OF THE DAYMON TUE WED THU FRI SAT SUN

Input/output parameterType of the day of the weekDefines whether or not a processing operation is to be performed forthe day of the week.If a calendar is to be set up using SYSTEM symbolic dates, the typeWORK must be specified for at least two days of the week.{WORK | NWRK | FREE}

If nothing is specified, WORK is used.

WORK Day on which processing is performed.The day is taken into consideration during planning using relativesymbolic start dates (symdat ±nn).The symbolic dates for the calendar day are used during planning.

Note

The type WORK for a day of the week is displayed using BLANK(not FREE or NWRK) for the MODIFY- and SHOW-CALENDARstatements.

NWRK Day on which processing is performed.The day is not taken into consideration (i.e. is skipped) duringplanning using relative symbolic start dates (symdat ±nn). Noprocessing using relative SYMDATs is planned for this day.The symbolic dates for the calendar day are used during planning.

FREE Day on which no processing is performed.The day is not taken into consideration (i.e. is skipped) duringplanning using relative symbolic start dates (symdat ±nn).The symbolic dates for the calendar day are not used duringplanning.

Note

The type of a calendar day (WORK, NWRK, FREE) can be changedusing MODIFY-CALENDAR (AVC002 mask).

1) SYSTEM symdat ‘Current day of the month“ for the 11.5.1998

SYSTEM symdat in the calendar day record = *EVDM11

2) SYSTEM symdat ‘nnth. day of the month mm“ for the 11.5.1998

SYSTEM symdat in the calendar day record = *EVDM11M05

242 U5184-J-Z125-7-76

Mask AVC001 CREATE-CALENDAR

SPECIAL NWRK OR FREE DATESInput/output parameterCalendar days to which another type is to be assigned, which isdifferent from the default assignment for the day of the week.Input form: (dd.mm.yy) = {NWRK | FREE}

The specified date must be within the calendar limit dates .

Notes

– If the number of SPECIAL NWRK OR FREE DATES to bespecified is greater than the number of fields in the mask, theinput fields can be released for further input by means of thepaging function +.By entering +n or –n, it is possible to page forward or backwardby n SPECIAL NWRK OR FREE DATES respectively.

– If a calendar is to be set up using SYSTEM symbolic dates, atleast two working days (type WORK) must be defined within 14days.

SYSTEM-SYMDAT-NAMES:If SYSTEM symbolic dates are to be generated for the calendar (seeSYMDAT-NAME parameter), the names of the SYSTEM symbolicdates can be defined.If the statement is called using the SYMDAT-NAME=*NONEparameter, the input fields for the names of the SYSTEM symbolicdates are set to protected.

EVERY DAY Input/output parameterName for “every day“{name 1..8 | TGL}

EVERY WORKING DAYInput/output parameterName for “working day“{name 1..4 | WT}

DAY OF THE MONTHInput/output parameterName for “current day of the month“{name 1..4 | K}

WORKING DAY OF THE MONTHInput/output parameterName for “current working day of the month“{name 1..4 | A}

U5184-J-Z125-7-76 243


LAST WORKING DAY OF THE MONTHInput/output parameterName for “last working day of the month“{name 1..8 | ULTIMO}

Note

The names of the SYSTEM symbolic dates can be defined by theuser. Otherwise, the specified default names are used. The namesmust be different.

The names of the SYSTEM symbolic dates that are to be generatedadditionally are derived from the defined names.Special characters cannot be used in the names of the SYSTEMsymbolic dates.

244 U5184-J-Z125-7-76

MODIFY-CALENDAR

MODIFY-CALENDARModify calendar

The MODIFY-CALENDAR statement is used to edit a calendar already contained in thecalendar library.

The start and end dates of the calendar, the free days and the symbolic dates contained inthe calendar can be edited, or new symbolic dates can be entered in the calendar. Calendarsections can be copied within the calendar or from a different calendar.

The processing of a calendar is controlled using the NEXT parameter (AVC002 mask).USER symbolic dates can be edited and copied, while calendar limit dates and the type ofa calendar day can be modified.

In the case of symbolic start dates, a distinction is made between the start dates defined bythe user with MODIFY-CALENDAR (USER symbolic dates) and the start dates generatedusing CREATE-CALENDAR (SYSTEM symbolic dates).

The USER symbolic datets of a calendar day can be edited using the marks A (Add) and D(Delete) and the SYMDAT-NAME operand, or using the mark S (Select) with EDT.

The SYSTEM symbolic dates are updated automatically when the type of calendar day ischanged.

CALENDAR-NAME=calendar

Name of a calendar contained in the calendar library. This causes immediate display of thespecified calendar (AVC002 mask).If the calendar name is specified via a partial qualification by a privileged user (finalcharacter *), this produces an overview of all calendars from the calendar library whosenames begin with the partial qualification (AVC010 mask).

Notes

– Privileged users can access any calendars by specifying the calendar name.

– Normal users can only modify the calendar assigned to them. Thus, it is superfluous forthem to specify the calendar name.

MODIFY-CALENDAR

[CALENDAR-NAME=calendar]

[,SYMDAT-NAME=symdat]

[,PERIOD-NAME=period | (dd.mm.yy [,dd.mm.yy] ) ]

U5184-J-Z125-7-76 245

MODIFY-CALENDAR

SYMDAT-NAME=symdatName of a symbolic date to be entered in or removed from the calendar on freely selectabledays. Special characters are prohibited in symbolic date names.

Only the name of a USER symbolic date can be specified.The user cannot edit SYSTEM symbolic dates that were generated for the calendar.

The names of the days of the week and the attribute “FREE, NWRK or WORK“ are perma-nently assigned symbolic date entries or reserved names.The maximum length of "symdat" is 20 characters.

If relative symbolic start dates in the form symdat±nn are used in the net planning phase,the maximum length of “symdat” is 17 characters.

When a calendar with no SYSTEM symbolic dates is processed, up to 98 symbolic datenames can be used for each calendar day.

When a calendar with SYSTEM symbolic dates is processed, up to 48 symbolic date namesare permitted for each calendar day.

If SYMDAT-NAME is specified when copying a calendar section, only the specified name iscopied.

PERIOD-NAME=Specifies a period (time span). This operand serves to display a single calendar and not toselect calendars. It is not interpreted unless specified together with a fully qualified calendarname.The period determines which section of the calendar is to be edited. It must be createdbeforehand by means of CREATE-PERIOD.

PERIOD-NAME=periodSymbolic name of the period.

PERIOD-NAME=(dd.mm.yy[,dd.mm.yy])Real time limits defining the start and end dates of the period (boundary dates). They mustlie within the absolute limits of the calendar.

246 U5184-J-Z125-7-76

Mask AVC002 MODIFY-CALENDAR

AVC002 - Display a calendar for modification

NEXT Input/output parameterThe processing of a calendar is controlled, depending on the valueof the NEXT parameter.

S (Symdat) Process USER symbolic datesThe following entries are possible in the mark column:A and D with the operand SYMDAT-NAMES for EDT processing

C (Copy) Copy USER symbolic dates of a calendar sectionEntries can be made in the following parameter fields:COPY-TO CAL-DATE, COPY-FROM-CALENDAR, FROM-DATEand TO-DATE

T (Type) Change the type of the calendar dayEntries can be made in the TYPE parameter field.

E (Expand) Change the calendar limit datesEntries can be made in the FIRST/LAST-CALENDAR-DATEparameter fields.

The NEXT parameter can only be changed if no entries weredefined for the processing operation using the input fields, of if theselected operation has been performed. If the operation does nothave to be performed, the entries must be canceled or deleted.

It is possible at all times to position the display using the + or -marks and to control the display using the LINES/DAY, FROM-DATEand TO-DATE parameters.

CALENDAR-NAME Output parameter.Name of the calendar.

FIRST-CALENDAR-DATEInput/output parameter.First day of the calendar (dd.mm.yy).

LAST-CALENDAR-DATEInput/output parameter.Last day of the calendar (dd.mm.yy).

Note

If a calendar with SYSTEM symbolic dates was created (CREATE-CALENDAR with SYMDAT-NAME=*STD/*ALL), the calendar mustbegin at the first of a month (FIRST-CALENDAR-DATE) and end at

U5184-J-Z125-7-76 247

MODIFY-CALENDAR Mask AVC002

the last day of the month (LAST-CALENDAR-DATE). This must betaken into consideration when changing the boundary dates of sucha calendar.

The type of day of the week defined by the user (CREATE-CALENDAR, mask AVC001, TYPE OF THE DAY parameter) isused for defaulting if the size of the calendar is increased bychanging the calendar limit dates.

M Input parameterMark column for selecting the calendar day to be processed.

A (Add) The SYMDAT-NAME specified as an operand is to be added to thelist of USER symbolic dates.

D (Delete) The SYMDAT-NAME specified as an operand is to be deleted fromthe list of USER symbolic dates.

S (Select) Selects a calendar day to be processed using EDT. Only USERsymbolic dates can be created or edited.

The S marks are saved and processed with EXECUTE.Only calendar days whose dates fall within the limited time span(FROM/TO-DATE) are edited.

DATE Output parameter.Date of the calendar days from FIRST-CAL-DATE to LAST-CAL-DATE.Each display encompasses the calendar section selected via theoperation code, the PERIOD-NAME operand or the FROM-DATE orTO-DATE parameter.The date is output in the form dd.mm.yy.

DAY Output parameter.Day of the week to be assigned to the date.The displayed names of the days of the week are valid symbolicdates. The following abbreviations are used:MON, TUE, WED, THU, FRI, SA, SUN

DAY is not included when a calendar section is copied.

248 U5184-J-Z125-7-76


TYPE Input/output parameterType of the calendar day

WORK Production day; planning for this dayThe day is taken into consideration during planning using relativesymbolic start dates (symdat ±nn).The symdats of the calendar day are taken into consideration duringplanning.

Note

The type WORK for a calendar day is indicated in the statements asBLANK (not FREE or NWRK).The type FREE or NWRK for a calendar day can be reset byentering WORK.

FREE Production-free calendar day; no planning for this dayThe day is not taken into consideration (i.e. skipped) during planningusing relative symbolic start dates (symdat ±nn).No processing using relative symbolic dates is planned for this day.The symbolic dates of the calendar day are not taken into consider-ation during planning.

NWRK Planning for this dayThe day is not taken into consideration (i.e. skipped) during planningusing relative symbolic start dates (symdat ±nn).No processing using relative symbolic dates is planned for this day.The symbolic dates of the calendar day are taken into considerationduring planning.

*DEL FREE/NWRK is reset.

Note

If the type of a calendar day is changed, the SYSTEM symbolicdates of the relevant calendar section are deleted and are regen-erated for all the calendar days in the section.

At least two working days (TYPE=WORK) must be defined within 14calendar days (two days without TYPE=NWRK or =FREE).

SYMDATE Output parameterThe SYMDAT-NAMEs (symdats) assigned to the date are displayedin the form of a list, separated by commas. If one line is not enough,two or more lines are used for the display, depending on the LINES/DAY parameter.The SYSTEM symdats generated for the calendar day are markedwith an asterisk (*) as the first character.

U5184-J-Z125-7-76 249


Note

Only the name of a USER symbolic date (first character is not *) canbe specified for the SYMDAT-NAME operand (mark A and D). Thisis not matched with the generated SYSTEM symbolic dates (nameof the SYSTEM symdat with no *).

If a calendar with no SYSTEM symbolic dates is processed, up to98 USER symbolic dates are permitted for each calendar day.

If a calendar with SYSTEM symbolic dates is processed, up to 48USER symbolic dates are permitted for each calendar day.The name of a SYSTEM symbolic date with no * must be specifiedin the net.

During net planning (CREATE-PLAN-NET) the symbolic datesspecified in the net are first matched with the SYSTEM symbolicdates. If the net symbolic date is found in the SYSTEM symbolicdates, a search is no longer performed in the USER symbolic datesof the calendar day.

FROM-DATE Input/output parameter.The calendar section beginning with FROM-DATE (dd.mm.yy) is tobe displayed (see the notes for TO-DATE).

The calendar section starts with the current date if the PERIOD-NAME operand has not been specified or if the date is in thecalendar.

If the PERIOD-NAME operand has been specified, the calendarsection begins with the start date of the period (for PERIOD-START-DATE see the section dealing with periods in “AVAS Job Handling“[2].

When a calendar section is copied, the start date is determined byFROM-DATE.

Note

The calendar days are displayed as and from the current date.The current date is not set in the FROM-DATE field if PERIOD-NAME is not specified. FIRST-CAL-DATE is then assigned toFROM-DATE so that it is possible to page back to the beginning ofthe calendar without changing FROM-DATE.

TO-DATE Input/output parameter.The calendar section up to TO-DATE (dd.mm.yy) is to be displayed.

When a calendar section is copied, the end date is determined byTO-DATE.

250 U5184-J-Z125-7-76


Notes

– FROM-DATE and TO-DATE must lie within the period specifiedin the operand field. This makes it possible to shift theprocessing window without having to page through all the days.

– If the start and end dates of the calendar (FIRST-/LAST-CALENDAR-DATE) are modified, the calendar is displayed fromthe start date after the modification has been made.

– If the start and end dates of the calendar section delimited byFROM-DATE and TO-DATE are modified, the calendar sectionon display remains intact, provided the days it displays liebetween FROM-DATE and TO-DATE. In order to display thecalendar section as of a new, earlier FROM-DATE, CMD:FIRSThas to be specified.

COPY-TO-CAL-DATE Input/output parameterStart date of the calendar section (dd.mm.yy) to which the USERsymbolic dates are to be copied.

Either all USER symbolic dates of the calendar section delimited byFROM-DATE and TO-DATE are copied, or the symbolic datespecified as an operand is copied.If a calendar was not defined using the COPY-FROM-CALENDARparameter, the original section and the target section must notoverlap.

When a calendar section is copied to COPY-TO-CAL-DATE, thecalendar must first be extended to such an extent using LAST-CAL-DATE that all days lie within the limits of the calendar.

When a calendar section is copied, the SYSTEM symbolic datesthat may have been defined for the calendar days and the type ofthe day are not automatically copied at the same time.

COPY-FROM-CALENDARInput/output parameterName of a calendar from which the USER symdats of a calendarsection are to be copied.Either all USER symbolic dates of the calendar section delimited byFROM-DATE and TO-DATE are copied, or the symbolic datespecified as an operand is copied.When a calendar section is copied, the SYSTEM symbolic datesthat may have been defined for the calendar days and the type ofthe day are not automatically copied at the same time.

U5184-J-Z125-7-76 251


Note

Only privileged users can access any calendars by specifying acalendar name. The name of a calendar that is currently beingprocessed cannot be specified.Normal users can only edit calendars assigned to them and do nottherefore enter any calendar names.

LINES/DAY Input/output parameterMaximum number of mask lines to be displayed for each calendarday.{1 | 2 | .. 9}

Notes

– The AVC002 mask always contains the first line of a calendar day at the beginning ofthe work window. It is possible to page forward or backward by n calendar days usingthe operation characters +n and –n respectively.

– If a calendar day is marked with –, it becomes the last completely displayed day whena calendar day occupies more than one line of the work window on account of thenumber of symbolic dates present (see also maximum number of mask lines using theLINES/DAY parameter).

– If not all the symbolic dates can be displayed for a calendar day because of the definedmaximum number of mask lines, this is not indicated by a message.

252 U5184-J-Z125-7-76


AVC004 -Output on termination of EDTDisplay the parameters of a calendar day

The parameters in the AVC004 mask are the same as those in the AVC002 mask.

All displayed parameters are output parameters. They are simply used to guide the users.Users can decide

– whether the modified USER symbolic dates of the calendar day are to be written back(CONTINUE) or

– whether the changes implemented using EDT are to be “forgotten” (IGNORE).

Notes

– Of all the data relating to the calendar day displayed in the EDT, only the USERsymbolic dates can be changed. Any other changes that are made are lost.

– The USER symbolic dates of a calendar day are displayed after the comment line ‘*9....‘in the EDT.The SYSTEM symbolic dates of a calendar day (comment line ‘*3.‘) cannot be changed.

– One USER symbolic date is displayed per line (starting with position 1).

– Following HALT in the EDT, the USER symbolic dates are read in and checked.Only lines that do not begin with * (comment) in the first position are interpreted assymbolic date lines.Only one symbolic date per line can be copied (starting with position 1).

– If a number of symbolic dates exist, the copy operation is rejected and a correspondingmessage is displayed. The same applies for formally invalid symbolic dates, or if themaximum number of symbolic dates is exceeded.SYSTEM symbolic dates cannot be transferred. Their names have been defined andreserved for the calendar using the CREATE-CALENDAR statement.EDT is not terminated in the event of an error. The error message is displayed in workfile0 and the user must correct the error before EDT can be terminated. (If the error is notcorrected, the workfile 0 must be deleted and OPC:IGNORE must be entered in maskAVC004.)

– If only comment lines (* in first position) exist, the statement assumes that all USERsymbolic dates are to be deleted. If an empty file is transferred using EDT, all USERsymbolic dates of a calendar day are deleted using the CONTINUE operation.SYSTEM symbolic dates of a calendar day are not affected by the deletion.

U5184-J-Z125-7-76 253


AVC010 - Overview of calendars

M Input parameter

S (Select) The marked calendar is displayed in the AVC002 mask for modifi-cation purposes.


DATE Output parameter.

Date of last modification.


UPDATED The calendar modified in the AVC002 mask was added to thelibrary.

NO-UPDATE Calendar processing was aborted in mask AVC002 by means ofRETURN. The modifications were ignored in the library.

254 U5184-J-Z125-7-76

SHOW-CALENDAR

SHOW-CALENDARDisplay calendar

The SHOW-CALENDAR statement enables the user to obtain a display of the entries in thecalendar. If the function authorization table is limited to the user’s own user group, only thecalendar assigned to the user group can be displayed.The range of days delimited by the boundary dates (preset via PERIOD-NAME) is displayedtogether with its associated symbolic dates.

The user can also display the data for a calendar day using EDT.

CALENDAR-NAME=calendarName of a calendar contained in the calendar library. This causes an immediate display ofthe specified calendar (AVC002 mask).If the calendar name is specified via a partial qualification by a privileged user (finalcharacter *), this produces an overview of all calendars from the calendar library whosenames begin with the partial qualification (AVC010 mask).

Notes

– The privileged user can access any calendars by specifying the calendar name.

– The normal user can only modify the calendar assigned to him. Thus, it is superfluousfor him to specify the calendar name.

PERIOD-NAME=Specifies a period (time span).The period determines which calendar section is to be processed.This operand is only permitted in conjunction with a fully qualified calendar name.

PERIOD-NAME=periodSymbolic name of the period.

PERIOD_NAME=(dd.mm.yy[,dd.mm.yy])Real time limits determining the start and end dates of a period. They must lie within theabsolute limits of the calendar. If the "right" calendar limit is not specified, only one calendarday is displayed.

SHOW-CALENDAR


[,PERIOD-NAME=period | (dd.mm.yy [,dd.mm.yy] ) ]

U5184-J-Z125-7-76 255

SHOW-CALENDAR Masks AVC010/AVC002

In the AVC010 mask the privileged user is given a list of all existing calendars.

The RESULT parameter is irrelevant in this context. For a description of the remainingparameters see MODIFY-CALENDAR.The calendar marked in the AVC010 mask is displayed in the AVC002 mask.

AVC002 - Display a calendar section

M Input parameterMark column for selecting the calendar day to be displayed.

S (Select) Selects a calendar day to be displayed using EDT.The S marks are saved and processed during EXECUTE.Only calendar days whose date falls within the delimited time span(FROM/TO-DATE) are displayed.

LINES/DAY Input/output parameterMaximum number of mask lines to be displayed for each calendarday.{1 | 2 | .. 9}

Notes

– The calendar section begins with the current date if the PERIOD-NAME operand hasnot been specified.The current date is not set in the FROM-DATE field. FIRST-CAL-DATE is then assignedto FROM-DATE so that it is possible to page back to the beginning of the calendarwithout changing FROM-DATE.

– If the PERIOD-NAME operand has been specified, the calendar section begins with thestart date of the period (for PERIOD-START-DATE see the section dealing with periodsin “AVAS Job Handling“ [2].

– The parameters FROM-DATE and TO-DATE can be used to shift the section of theselected calendar.

– A calendar day (not a symdat line) always appears at the beginning of the work windowin the AVC002 mask. The operation characters +n and -n can be used to page forwardsand backwards by n calendar days.

– If a calendar day is marked with –, it becomes the last completely displayed day whena calendar day occupies more than one line of the work window on account of thenumber of symbolic dates present (see also maximum number of mask lines using theLINES/DAY parameter).

– If not all the symbolic dates can be displayed for a calendar day because of the definedmaximum number of mask lines (LINES/DAY parameter), this is not indicated by amessage. The meaning of the other parameters is described under the MODIFY-CALENDAR statement.

256 U5184-J-Z125-7-76

COPY-CALENDAR

COPY-CALENDARCopy calendar with symbolic dates

The COPY-CALENDAR statement makes a copy of an existing calendar.

This statement can only be executed by a privileged user.

The name under which the copy is to be stored is left to the user’s discretion. If a calendarwith the name specified under COPY-CALENDAR-NAME already exists, it can beoverwritten by entering YES in the OVERWRITE column.

All dates are stored with century specifications in the copied calendar.

CALENDAR-NAME=calendarName of a calendar contained in the calendar library. This causes an immediate display ofthe specified calendar (AVC012 mask).If the calendar name is specified via a partial qualification (final character *), this producesan overview of all calendars from the calendar library whose names begin with the partialqualification (AVC012 mask).

Note

If no calendar name is specified, the calendar assigned to the user is displayed in theAVC012 mask.

COPY-CALENDAR


U5184-J-Z125-7-76 257

COPY-CALENDAR Mask AVC012

AVC012 - Copying calendars

M Input parameter.

Y(Yes) The marked calendar is to be copied.

N(No) The marked calendar is not to be copied. All calendars not markedwith N are copied.


COPY-CALENDAR-NAMEInput parameter.Name of the calendar copy.


OVERWRITE Input parameter.

NO An existing calendar will not be overwritten. The copy operation canbe restarted after changing COPY-CALENDAR-NAME.

YES An existing calendar will be overwritten.If nothing is specified here, NO is assumed.

RESULT Output parameter.Acknowledgment for the completed action.

COPIED The marked calendar was copied.

NO-COPY The calendar was not copied since there already exists a calendarunder COPY-CALENDAR-NAME and overwriting was notrequested.

258 U5184-J-Z125-7-76

DELETE-CALENDAR

DELETE-CALENDARDelete calendar

The DELETE-CALENDAR statement deletes calendars from the calendar library.

If the function is executed by a privileged user, the assignments to the user groups are notchecked.

Normal users can only delete the calendar of their own user group.

Deleting a calendar has no effect on nets which have already been planned.

CALENDAR-NAME=calendarName of a calendar contained in the calendar library. This causes an immediate display ofthe specified calendar (AVC010 mask).If the calendar name is specified via a partial qualification (final character *), this producesan overview of all calendars from the calendar library whose names begin with the partialqualification (AVC010 mask).

Note

If the operand is not specified, the users are only shown the calendar assigned to them.

AVC010 - Overview of calendars

M Input parameter.

Y(Yes) The marked calendar is to be deleted.



RESULT Output parameter.Acknowledgment for the completed action.

DELETED The calendar indicated was deleted.

NO-DELETE The calendar could not be deleted because it was being processedby another user at the time.

DELETE-CALENDAR


U5184-J-Z125-7-76 259

6 Coupling AVAS with MARENWith the aid of the MARENAV module it is possible to couple the two self-containedsoftware products AVAS and MAREN [8] (as of Version 4.0). This coupling is performed bycalling MARENAV at the computer center exit AVEX7102 of the AVAS component "releasefor production". This module contains, among other things, the MAREN program interfaceand carries out the following actions, which are explained further in the course of thischapter:

– perform volume checks– enter VSNs in the JCL– create volume listings.

Performing volume checks

All magnetic tape devices and cartridges required by a net (referred to below as "volumes"or "tapes") are checked by MARENAV as to their availability. MARENAV fetches the VSNsof these volumes from various sources:– MAREN catalog– system catalog (TSOSCAT)– DMS commands issued in the individual jobs of a net.

In the latter case, the following commands are involved:– /FILE– /CREATE-FILE– /CREATE-FILE-GENERATION– /IMPORT-FILE– /MODIFY-FILE-ATTRIBUTES– /MODIFY-FILE-GENERATION-SUPPORT– /SET-FILE-LINK

Whether a volume is available is determined on the basis of the following criteria:

1. VSN contained in the MAREN catalog?

2. If so, is it a reserved volume (RESERVED or PRIVATE)?

260 U5184-J-Z125-7-76

MARENAV

If desired, checking these criteria can be avoided by means of the MAREN parameterFOREIGN-TAPE-CHECK=NO. If this parameter is set to YES and if one of the aforemen-tioned checks is negative, the release for production of MARENAV is aborted. If the volumeis available, i.e. reserved and entered in the MAREN catalog, two further conditions arechecked:

3. The device type from the MAREN archive entry must match the device type specifiedin the DMS command or the one taken from the file catalog entry.

4. The volume must not be exported.

If one of these checks is negative, the release for production is not aborted; instead, a noteto this effect for the VSN in question is included in the two volume listings created byMARENAV.

Other circumstances which can cause the release for production to abort:

– A file consists of more than 255 volumes.

– With a multivolume file, not all of the follow-up reels have been entered in the MARENcatalog.

– Not all VSNs of a multivolume file are assigned to the same ID in the MAREN catalog.

– The MAREN system is not operable (e.g. control program not loaded, MAREN catalogclosed).

– On the basis of the CLOSE indicator in the archive entry of a volume MARENAV deter-mines that the associated file was not (or not properly) closed at creation time. If this isthe case, the file involved is an input file since the wildcard (#VOL#) was specified in theDMS command.

As a rule, the VSNs of a tape file are only checked once within a net, namely at the firstcommand that addresses the volume in question. If a volume is used once again in a subse-quent job of the same net, no further MAREN checks are performed.

If the volumes reserved by MAREN are output tapes or cartridges, none of the aforemen-tioned checks is required. MAREN has already carried out all the checks during reservation.

It is only possible to carry out the volume checks in a meaningful way if the archive entriesin the MAREN catalog are up to date, i.e. reflect the actual file status of the associatedtapes. This is no longer the case, for instance, if the tapes were exported and written in adifferent computer center, or if tape processing ran temporarily without the MAREN systemand the necessary updates were not entered afterwards in the MAREN catalog.

Whenever entries from the file catalog (TSOSCAT) are used for purposes of checking, it isalways assumed that the current catalog entry also exists in exactly the same form at thetime the net is executed. Thus, if a VSN not contained in the MAREN catalog is entered ina system catalog entry of a file and the MAREN parameter FOREIGN-TAPE-CHECK is setto YES, release for production will be aborted.

U5184-J-Z125-7-76 261

MARENAV

The catalog entry of a file will not be evaluated if

– the entry was created with the /IMPORT-FILE command (file from private volume)

– the VOLUME-LIST operand has been used in the /SET-FILE-LINK command

– one of the variables (#VOL#) or (#SCR#) has been specified in the file assignment withthe VOLUME operand

– the file has already been addressed in the net.(In this case, the file may have been written to and any catalog entry existing at the timeof SUBMIT will no longer be up to date at execution time.)

If a volume is contained in the file catalog entry but has not yet been written to(/SHOW-FILE-ATTRIBUTES displays the VSN in parentheses), this fact is noted in thevolume lists.

Before the file catalog entry is read, the specified file name is checked for the presence ofa catalog ID. If a catalog ID has been specified, this will be used for reading; if not, the filename will be extended by the catalog ID passed by AVAS at computer center exitAVEX7102.

Example

The catalog ID :2: is passed to MARENAV at the computer center exit. A job in the netcontains the command

/SET-FILE-LINK LINK=LINK01,FILE-NAME=$UG01.FIL1.

The catalog entry reads as follows:

/SHOW-FILE-ATTRIBUTES :2:$UG01.FIL1 .

In this connection it should be noted that this extension of the file name may be errored ifan MPVS system is set up on the target processor.A different catalog ID may be entered for user ID UG01 on the target processor than the IDpassed by AVAS at the computer center exit. Consequently, on release of the net thecatalog entry of a different file will be read than that which is actually referenced onexecution of the net.

Generally speaking, a net is not released under the system administrator ID TSOS.Therefore it is not possible to ascertain the default catalog ID of the target processor byreading the user entries. A correct extension algorithm for the file names cannot thereforealways be guaranteed.

262 U5184-J-Z125-7-76

MARENAV

If DMS reports one of the following errors on reading the catalog entry, release of the net isaborted with the message CATALOG (&00) NOT ACCESSIBLE.

DMS0501 REQUESTED CATALOG NOT ACCESSIBLE. COMMAND REJECTED

DMS0502 REQUESTED CATALOG IN QUIET OR HOLD MODE. WAITING TIME IS OVER. COMMAND NOT PROCESSED

DMS0503 MRSCAT CONTAINS INCORRECT INFORMATION. COMMAND REJECTED

DMS0504 CATALOG MANAGEMENT SYSTEM ERROR. COMMAND TERMINATED

DMS0505 CMS RETURNED ERROR IN THE MRS COMMUNICATION FACILITY TO THE COMMAND PROCESSING

DMS0512 REQUESTED CATALOG CANNOT BE FOUND. COMMAND TERMINATED

U5184-J-Z125-7-76 263

MARENAV

Entering VSNs in the JCL

The following wildcards can be used in the BS2000 commands (see page 259) to enterVSNs in the JCL of the jobs:

– (#VOL#) or (#VOL#-n) for input tapes

– (#SCR#) or (#SCR#,n) for output tapes

These wildcards may not be used as comments in the DMS commands evaluated byMARENAV. When entered, the VSNs are always enclosed in parentheses, even if there isonly one VSN.

If MARENAV is to be used to good effect in AVAS with multiprocessor capability, particularlywhen wildcards are employed, the following requirement must be met:All processors on which the jobs referenced by a net release are to be executed must beconfigured into a MAREN network, i.e. using the same MAREN catalog.

Otherwise, volumes are reserved by (#SCR#), for example, at the time of the net releasewhich are not then contained in the MAREN catalog of the target processor upon subse-quent execution of the net. This will result in the MAREN system aborting commands.

Note

When MARENAV enters VSNs in the JCL, the tape is reserved for the execution ID ofthe job. For this reason, it is no longer permitted to modify this ID by means of the AVASstatement MODIFY-SUBMIT-NET (NET-USER or USER operand).

Entering VSNs for input tapes

In the command

/IMPORT-FILE SUPPORT=TAPE(VOLUME=(#VOL#),DEVICE-TYPE=device,FILE-NAME=file)

MARENAV substitutes a concrete VSN for the wildcard (#VOL#).If a multivolume file is involved, this variable is replaced by a VSN list. MARENAV fetchesthe VSNs from the MAREN catalog. If this catalog contains a file more than once, the mostrecent version of the file is selected. It is also optionally possible to request an earlierversion by entering (#VOL#-n), where "n" may take any value between 0 and 9999. Forexample, if VOLUME=(#VOL#-1) is specified, MARENAV will select the next-to-last versionof the file and enter the associated VSNs in the relevant DMS command. Since, in theMAREN catalog, the same file name may occur in the archive entries of different IDs,MARENAV must be told which ID, and therefore which VSN, has to be selected in this case.This can be done by means of the following command:

264 U5184-J-Z125-7-76

MARENAV

/REMARK #UID#={*OWN | *ALL | userid}

*OWN Default value: MARENAV selects only those VSNs which have the specifiedfile name in the archive entry and are assigned either to the user ID fromthe file name or to the execution ID. The execution ID is determined asfollows:

– If the nameJENT field in the AVAS communication area has the value"nameJENTJ" (specification ENTER-PARAMS=NET in the netdescription), the ID specified in the nameJUSE field is used.

– However, if the nameJENT field has the value "nameJENTL" (specifi-cation ENTER-PARAMS=LOGON in the net description), the IDspecified in the /SET-LOGON-PARAMETERS command is used as theexecution ID.

At least one of these three positions must have an ID, otherwise release forproduction will be aborted. As with the "userid" value, *OWN likewiseenables a selection specific to a single ID. However, the *OWN value offersthe advantage of job neutrality, i.e. when an ID is changed it is notnecessary to change the JCL with regard to the /REMARK #UID#command.

*ALL When VSNs are selected, the IDs under which they are entered in theMAREN catalog are not taken into account. This parameter must beselected whenever the procedures employed in a computer center allow thepossibility that individual versions of one and the same file can be createdunder different IDs.

userid MARENAV selects only those VSNs which have the specified file name inthe archive entry and are assigned to the user ID "userid". This parametermust be selected whenever a file name occurs under more than one ID inthe MAREN catalog but different files are involved. If MARENAV cannotlocate an archive entry with this file name under the specified ID, release forproduction is aborted.

The VSN selection made by means of /REMARK #UID# is only valid until the job has termi-nated. Within a job, as many additional /REMARK #UID# commands as desired can beused. The selection remains valid until superseded by a new one made by the following/REMARK #UID# command.

U5184-J-Z125-7-76 265

MARENAV

Entering VSNs for output tapes

In the command

/CREATE-FILE FILE-NAME=file,SUPPORT=TAPE(VOLUME=(#SCR#),DEVICE-TYPE=device)

MARENAV reserves a free tape and substitutes the received VSN for the wildcard (#SCR#)in the relevant DMS command. The user ID for which the tape is reserved is determined inthe same way as is possible for input tapes using /REMARK #UID#=*OWN. In other words,if the file name specified in the command does not contain an ID, a reservation takes placefor the execution ID. This is determined as follows:

– If the field nameJENT in the AVAS communication area has the value "nameJENTJ",the execution ID is stored in the nameJUSE field.

– If the field nameJENT has the value nameJENTL, the execution ID corresponds to theID specified in the /SET-LOGON-PARAMETERS command.

If the ID is lacking at all these locations, MARENAV will abort the release for production.

By default, the free volumes are reserved from the storage location defined by means of theMAREN parameter DEFAULT-HOME-LOCATION (MARENADM statement//RESERVE-FREE-VOLUME ...,HOME-LOCATION=*STD).If a reservation from a different storage location is to be effected, this must be previouslydefined in the job concerned:

/REMARK #LOC#=storage-location

Note that no blanks may be entered before or after the = sign. If the release for productionis to take place on a computer running a version of MAREN Î V5.0A), the name of thestorage location must be entered in the storage location table of the MAREN parameters.

The definition made by means of /REMARK #LOC# always remains in force only until theend of the job. The reservation storage location can be changed as often as required ineach job. If another reservation is to be made from DEFAULT-HOME-LOCATION within ajob, this will be effected by means of the statement /REMARK #LOC#=*STD.

With a multivolume file, provision can also be made for two or more tapes. For example,when VOLUME=(#SCR#,3) is entered, MARENAV reserves three tapes and substitutes aVSN list (vsn1,vsn2,vsn3) for the wildcard. In this way, up to 255 volumes can be reservedat once.

The date produced by adding the start time specified by EARLIEST-START to the defaultretention period set in the MAREN parameter DEFAULT-FREE-DATE is used as the releasedate.

As with tape processing in BS2000 (DMS), these volumes are given the attribute USER-ACCESS=FOREIGN-READ-ONLY in the archive entry, i.e. they can only be read-accessedfrom other IDs. This presetting can be changed if necessary via the MAREN computercenter exit.

266 U5184-J-Z125-7-76

MARENAV

Handling continuation lines

If, with multivolume files, the insertion of VSNs makes the command line sent to MARENAVtoo long, the command or command portion will be replaced by two or more command lineswithout any special arrangements required on the part of the user.

Creating volume lists

During release for production, MARENAV creates the following three files for each net:

– transport list for the AV staff (file name beginning with TRS)

– tape mount listing for the operator (file name beginning with OPR)

– shift procedure for the archivist (file name beginning with PRC).

These files are SAM files, of which the first two contain print control characters(printout with /PRINT-FILE FILE-NAME=..., LAYOUT-CONTROL=PARAMETERS(CONTROL-CHARACTERS=EBCDIC)).

Since on SUBMIT, MARENAV only receives from AVAS the catalog IDs of the targetprocessors but the storage locations assigned to the respective target processors are to beinserted in the volume lists and specifically in the shift procedure, an assignment table mustbe made available to MARENAV. This table should be stored in a SAM file; the individualrecords in this file should have the following format:

4 bytes Catalog ID of the target processor, padded on the right with blanks ifnecessary.

1 byte Blank as separator.

8 bytes Storage location assigned to the target processor, padded on the right withblanks if necessary. The data type of the storage location name must be"alphanumeric", i.e. it may contain only letters, digits and the specialsymbols $, # and @. If the storage procedure is running in a version ofMAREN < 5.0A, the storage location name must be entered in the storagelocation table of the MAREN system. If this is not the case, the //MODIFYstatement would be rejected with the message INVALID LOCATION onexecution of the storage procedure.

For those cases in which a catalog ID is neither specified in the file name nor passed byAVAS at the computer center exit, a file record with a catalog ID consisting of four blanksmust be defined.

U5184-J-Z125-7-76 267

MARENAV

Example of individual file records

C3 CPU003 CI02 DA12ZE02 1 DVA001 2 DVA002 CENTRAL

The storage location file must be assigned with the link name MARENAVL (/SET-FILE-LINKLINK-NAME=MARENAVL,FILE-NAME=storage-location-file) in the procedure to be calledby the user for initiating the AVAS dialog (SYSPRC.AVAS.040). At the computer center exit,MARENAV uses RDTFT to ascertain the name of the file and fetches the required infor-mation from it.

If no file with the link name MARENAVL was assigned, the shift procedure is created witha variable &TEMPLOC, and the "TO-LOC" column in the transport and tape mount listingsremains empty. Thus, with all AVAS installations not in a multiprocessor systemenvironment, there is no need to create a storage location file. If in this case differentcatalog IDs are passed to MARENAV, a /REMARK line with the following text is included inthe shift procedure:

* WARNING: DIFFERENT CATIDS USED DURING SUBMIT *

This is intended to indicate that the volumes used in the net may possibly not be processedonly on one processor and so different storage locations would also need to be specifiedfor the procedure variable &TEMPLOC.

The release for production is aborted in the following cases:

– Although the storage location file is assigned it could not be opened, or a DMS erroroccurred during processing of the file.

– A storage location is not of data type "alphanumeric".

– There was no entry in the storage location file for a catalog ID passed to MARENAV.

268 U5184-J-Z125-7-76

MARENAV

Transport list

This file has the name TRS.AVAS.rcs.yymmdd.hhmmss.

rcs Name of the run control system.

yymmdd.hhmmss Date and time of day of the release for production.

This file contains a list of all VSNs belonging to a net, including those volumes which arerequired only in the case of a restart. It enables the job scheduler to ready all volumesrequired for execution of a net. If a volume is used more than once in a net, it neverthelessappears only once in the transport list.

The list header of this file contains the following information:

– file name of the volume list

– date and time of day of the release for production

– name of the net

– scheduled execution time

– number of all requests for scratch tapes of a particular device type

– number of all requested private tapes of a particular device type.

If a storage location file was assigned on release of the net (by means ofLINK=MARENAVL), the requests for scratch and private tapes will also be outputseparately according to storage locations.

Following the list header is a line for each VSN addressed in the net. This line has thefollowing structure:

– Hierarchy level (index) of the job requesting this VSN

– Job name from the /SET-LOGON-PARAMETERS command

– Catalog ID of the processor on which the volume is processed

– Current storage location of the volume (FROM-LOC)

– Storage location assigned to the catalog ID (TO-LOC). The volume is requested at thislocation on execution of the net. If no storage location file was assigned on release ofthe net, this column remains empty.

– VSN (volume serial number) of the volume

– Possibly a remark that the volume’s availability is restricted (e.g. the tape has beenexported) or that it is only required in the case of a restart.

U5184-J-Z125-7-76 269

MARENAV

The transport list is sorted according to

1. current storage location

2. VSNs of the volumes

On the basis of this list, job management staff can gather the tape sets addressed in a netand, if necessary, transport them to the system.

Example illustrating the structure of a transport list

A net bearing the name $UG01_SAL_NET_971219_160500 consists of only two jobs.The first job, with the name SALARY01, processes files from the pubset CI02. Thesecond job, with the name SALARY02, processes files from the pubset C3. A total ofseven volumes is required, where the tape with VSN Y1C002 is processed in both jobsand tape Y1A003 is still exported at the time of release for production. Two of thevolumes requested by the job SALARY02 are private tapes of type T6250. The nameof the processing system is RCS003. At the computer center exit, a storage location filewas assigned which contains the file records listed in the example on page page 267.

The transport list has the file name TRS.AVAS.RCS003.971218.113012 and is storedunder the user ID of the user releasing the nets for production.

*** FILE TRS.AVAS.RCS003.971218.113012 *** PAGE 1

DATE/TIME OF RELEASE: 97-12-18/11:30

NET NAME: $UG01.SAL.NET.971219.160500 EARLIEST START: 97-12-19/16:05

2 PRIVATE TAPES REQUESTED WITH DEVICE TYPE T6250 AT LOCATION CPU003

INDEX JOBNAME CATID FROM-LOC TO-LOC VOLUME REMARK

020 SALARY02 C3 CENTRAL CPU003 Y1A003 VOLUME IS EXPORTED

010 SALARY01 CI02 CENTRAL DA12ZE02 Y1B001

010 SALARY01 CI02 DVA11 DA12ZE02 Y1C002

010 SALARY01 CI02 DVA11 DA12ZE02 Y1D001

020 SALARY02 C3 DVA12 CPU003 Y1B003

270 U5184-J-Z125-7-76

MARENAV

Tape mount listing

This file has the name OPR.AVAS.rcs.yymmdd.hhmmss.


yymmdd.hhmmss Date and time of day of release for production.

Like the transport list, this file contains a list of all VSNs belonging to a net, including thosevolumes which are only required in the case of a restart. It tells the operator which volumesa net has requested. If a volume is requested more than once in a net, it will also appearmore than once in this list. Requests for scratch and private tapes are accompanied by thedevice type and, in the case of private volumes, by the specified number of such volumesin the file as well. The list header and the record structure of this file are identical to thosein the transport list of the job scheduler. However, sorting does not take place; instead, theVSNs and the scratch and private tape requests are listed in chronological order, i.e. in theorder in which they were requested by the individual jobs in a net at execution time.

Example illustrating the structure of a tape mount listing

The tape mount listing has the file name OPR.AVAS.RCS003.971218.113012 and isstored under the user ID of the user releasing the nets for production.

This file is structured as follows, using the same basic data as in the "transport list"example above:

*** FILE OPR.AVAS.RCS003.971218.113012 *** PAGE 1

DATE/TIME OF RELEASE: 97-12-18/11:30

NET NAME: $UG01.SAL.NET.971219.160500 EARLIEST START: 97-12-19/16:05

INDEX JOBNAME CATID FROM-LOC TO-LOC VOLUME REMARK

010 SALARY01 CI02 CENTRAL DA12ZE02 Y1B001

010 SALARY01 CI02 DVA11 DA12ZE02 Y1C002

010 SALARY01 CI02 DVA11 DA12ZE02 Y1D001

020 SALARY02 C3 CENTRAL CPU003 Y1A003 VOLUME IS EXPORTED

020 SALARY02 C3 CPU003 REQUESTED FOR 2 PRIVATETAPES

020 SALARY02 C3 CPU003 WITH DEVICE TYPE T6250

020 SALARY02 C3 DVA12 CPU003 Y1B003

020 SALARY02 C3 DVA11 CPU003 Y1C002

U5184-J-Z125-7-76 271

MARENAV

Shift procedure

This file has the name PRC.AVAS.rcs.yymmdd.hhmmss.


yymmdd.hhmmss Date and time of day of the release for production.

In this procedure file, the storage locations (TEMPORARY-LOCATIONS) in the MARENarchive entry are updated for all volumes required by a net. This shift procedure can becalled by the work scheduler when he transports the volumes from the individual archivesto the systems on which the jobs of the released nets are to run.As in the tape mount listing of the operator, each VSN is only listed once in this procedurefile.

If, for any volume, the shift triggered by the MARENADM statement //MODIFY-VOLUME-ATTRIBUTES cannot be carried out (e.g. because the volume is being processed onanother system), the procedure will not be aborted, but will continue normally with the nextVSN. However, it must be ensured that all volumes required to execute the net are actuallyavailable.

Example illustrating the structure of a shift procedure

The shift procedure has the file name PRC.AVAS.RCS003.971218.113012 and is storedunder the user ID of the user releasing the nets for production.

This file is structured as follows, given the same basic data as in the "transport list"example above:

/PROC A,(&MARENADM=MARENADM) /SYSFILE SYSDTA=(SYSCMD) /EXEC &MARENADM //MOD-VOL-ATTR VOL=Y1A003,TEMP-LOC=CPU003 //STEP //MOD-VOL-ATTR VOL=Y1B001,TEMP-LOC=DA12ZE02 //STEP //MOD-VOL-ATTR VOL=Y1C002,TEMP-LOC=DA12ZE02 //STEP //MOD-VOL-ATTR VOL=Y1D001,TEMP-LOC=DA12ZE02 //STEP //MOD-VOL-ATTR VOL=Y1B003,TEMP-LOC=CPU003 //END /ENDP

TEMP-LOC specifies the storage location to which the volumes are to be transferred.

272 U5184-J-Z125-7-76

MARENAV

Restrictions pertaining to MARENAV

The MARENAV functions cited are activated only if VSNs occur in one of the aforemen-tioned DMS commands (/CREATE-FILE etc.).

In the following cases, MARENAV does not initiate any actions:

– VSNs are specified in the /SECURE-RESOURCE-ALLOCATION command.

– VSNs occur in program statements.

– VSNs are to be replaced by job variable values.

– VSNs are specified in procedure variables.

– VSNs are addressed in a procedure which is started within a job via the /CALL-PROCEDURE command.

– In the /SET-FILE-LINK command, the VSNs contained in the TST entries are notchecked when the TAPE-SET-NAME operand is specified.

– The START-POSITION operand is not evaluated in connection with the availabilitychecks, i.e. all VSNs in a cataloged tape file are always checked, regardless of theselection made in the START-POSITION operand.

If a file is addressed more than once in a net, the volumes are only checked the first time itis addressed. Additional VSNs occurring in later assignments for this file are not checked,nor do they appear in the volume lists created by MARENAV.

Example illustrating further processing of a VSN in a net

A tape file is processed twice within a net. It is created as an output file in the first job andused as an input file in one of the subsequent jobs. If MARENAV is not used, the followingactions must be performed every time before starting the net:

– Reserve tapes with MARENADM or other archive routines.

– Enter VSNs of the newly reserved tapes in the ENTER file(s).

By using MARENAV you can skip each of these preliminary steps. Since the parameterVOLUME=(#SCR#,n) or VOLUME=(#VOL#) is already entered in the file assignmentswhen the ENTER files are created, no preliminary steps are needed before starting theproduction run.

U5184-J-Z125-7-76 273

MARENAV

Notes on retry runs

Certain special considerations should be noted with regard to the two different types of retryruns, using the RESTART-NET and REPEAT-NET statements:

1. Retrying an interrupted net via RESTART-NET

If tapes which were already being processed before abortion of the job or net are requestedwithin the framework of the RESTART run, then from the standpoint of the MAREN systemit is necessary before carrying out the restart to ensure that all the tapes archived in theMAREN catalog are available and that there are no restrictions impairing access:

– For all tapes written with a retention period specified, the retention period must be resetin the MAREN catalog by means of the MAREN/MARENADM statement//MOD-VOL-ATTR VOL=vsn,EXPIRATION-DATE=0 (provided it has not already expiredat the time of the restart).

– Between the abortion of the job and its restart using MAREN/MARENADM statements,no attributes which prevent renewed processing of these volumes may be applied to thetapes in the MAREN catalog (this should in any case be an improbable situation).Possible error causes would be, for example, modification of volume passwords, shiftingto remote storage locations, deletion of the VSNs from the volume catalog and releaseor exporting of the volumes.

– No MAREN parameters which result in a basic change in the checking of volume avail-ability should be modified in the interim (also improbable). The MAREN parameterFOREIGN-TAPE-CHECK, which indicates whether all volumes to be processed mustbe archived in the MAREN catalog, is particularly critical in this connection.

2. Retry run via REPEAT-NET

If a retry run is to be performed using REPEAT-NET it is necessary to ensure, as also in thecase of RESTART, that the retention period for all the output tapes archived in the MARENcatalog has already expired at the time of net execution. If this is not the case,EXPIRATION-DATE must first be reset with the aid of the MAREN statement //MODIFY-VOLUME-ATTRIBUTES.

If a file is to be further processed in one job or distributed over two or more jobs of a net,other actions may be required before REPEAT-NET. Two cases must be distinguished here:

– further processing of an input file

– further processing of an output file

274 U5184-J-Z125-7-76

MARENAV

Further processing an input file

A file update occurs in a net: a tape file created in the net most recently executed is read in,updated and written back to a new tape. Selection of the VSNs is performed with the aid ofthe wildcards (#VOL#) and (#SCR#).

Example for this job

/SET-LOGON-PARAMETERS/REMARK * ASSIGN TAPE INPUT FILE */IMPORT-FILE SUPPORT=TAPE(VOLUME=(#VOL#),DEVICE-TYPE=T6250,FILE-NAME=FILX)/SET-FILE-LINK LINK-NAME=IN,FILE-NAME=FILX/REMARK * ASSIGN DISK OUTPUT FILE */SET-FILE-LINK LINK-NAME=OUT,FILE-NAME=FILY/REMARK * COPY FILX (TAPE) TO FILY (DISK)/START-PROGRAM FROM-FILE=PROG1/REMARK * DELETE CATALOG ENTRY OF FILX */REMARK * RELEASE LINK NAME */EXPORT-FILE FILE-NAME=FILX/REMOVE-FILE-LINK LINK-NAME=IN/REMOVE-FILE-LINK LINK-NAME=OUT/REMARK * UPDATE FILX IN A SORT RUN */REMARK * OUTPUT FILX TO A NEW TAPE */SET-FILE-LINK LINK-NAME=SORTIN01,FILE-NAME=FILY/SET-FILE-LINK LINK-NAME=SORTIN02,FILE-NAME=FILZ/CREATE-FILE FILE-NAME=FILX,SUPPORT=TAPE(VOLUME=(#SCR#),DEVICE-TYPE=T6250)/SET-FILE-LINK LINK-NAME=SORTOUT,FILE-NAME=FILX/START-PROGRAM FROM-FILE=$SORT . . ./REMARK * DELETE CATALOG ENTRY OF FILX */EXPORT-FILE FILE-NAME=FILX/LOGOFF

If this run needs to be repeated because the tape output file created by the sort run isincorrect (e.g. an incorrect file was assigned with SORTIN02), the following should benoted:In REPEAT-NET, MARENAV would enter the VSN of the tape noted in the MAREN catalogfor the latest version of FILX in the JCL instead of the variable (#VOL#). This means thatthe sort output file created in the last, errored run would be further processed and not thestill correct file from the previous run (assigned here with LINK=IN). In order to prevent thisthe last, errored file version must be removed from the MAREN catalog. This can be donein several different ways. The simplest method consists in deleting the file name FILX in thearchive entry of the most recently created output tape by means of the MAREN statement//MOD-VOL-ATTR VOL=vsn, FILE=*NONE. If the volume is no longer required, the volumerelease date (FREE-DATE) and, if necessary, also the file release date (EXPIRATION-

U5184-J-Z125-7-76 275

MARENAV

DATE) must be reset at the same time by means of the MAREN statement//MOD-VOL-ATTR VOL=vsn, FILE-NAME=*NONE,FREE-DATE=0,EXPIR-DATE=0 in order that thevolume be released by the MAREN administrator during the next release run. If there aremultiple output tapes, this action must be performed for each individual tape.

Further processing an output file

A net comprises two jobs executing in succession; in the first job a tape file is created whichis used as an input file in the second job. Selection of the VSNs is again performed usingthe wildcards (#SCR#) (#VOL#). In this example the output may only be directed to a tapeand no archive entries containing the specified file names may be present in the MARENcatalog.

Example for job 1:

/SET-LOGON-PARAMETERS/REMARK * ASSIGN DISK INPUT FILE */SET-FILE-LINK LINK-NAME=PCIN,FILE-NAME=FIL1/REMARK * ASSIGN TAPE OUTPUT FILE */CREATE-FILE FILE-NAME=FIL2,SUPPORT=TAPE(VOLUME=(#SCR#),DEVICE=T1600)/SET-FILE-LINK LINK-NAME=PCOUT,FILE-NAME=FIL2/REMARK * COPY SELECTED RECORDS FROM FIL1 TO FIL2 */START-PROGRAM FROM-FILE=$PERCONSELECT COND=...END . . ./REMARK * DELETE CATALOG ENTRY OF FIL2 */EXPORT-FILE FILE-NAME=FIL2/LOGOFF

Example for job 2:

/SET-LOGON-PARAMETERS/REMARK * ASSIGN TAPE FILE CREATED IN FIRST JOB */REMARK * ASSIGN DISK INPUT FILE */IMPORT-FILE SUPPORT=TAPE(VOLUME=(#VOL#),DEVICE-TYPE=T6250,FILE-NAME=FIL2)/SET-FILE-LINK LINK-NAME=INPUT1,FILE-NAME=FIL2/SET-FILE-LINK LINK-NAME=INPUT2,FILE-NAME=FIL3/REMARK * ASSIGN DISK OUTPUT FILE */SET-FILE-LINK LINK-NAME=OUTPUT,FILE-NAME=FIL4/START-PROGRAM FROM-FILE=PROG2 . . ./REMARK * DELETE CATALOG ENTRY OF FIL2 */EXPORT-FILE FILE-NAME=FIL2/LOGOFF

276 U5184-J-Z125-7-76

MARENAV messages

If a net constructed in this way is to be repeated using REPEAT-NET, no particular actionsare required. It is advisable to release the volume created in the previous execution of thenet, assuming it is no longer required, (MAREN statement //MOD-VOL-ATTR VOL=vsn,FREE-DATE=0,EXPIR-DATE=0) and thus also remove the errored version of this file from theMAREN catalog.

Error messages from MARENAV

In the event of an error, MARENAV passes the message code of the MAREN message forpurposes of diagnosis, and possibly the VSN where the error occurred. If no preciseMAREN message code exists for the cause of the error, one of the following texts is sent:

CATALOG catid NOT ACCESSIBLE

The attempt to read the TSOSCAT entry of a file was rejected with one of the DMS errorcodes DMS0501 through DMS0505 or DMS0512, i.e. the corresponding catalog is notavailable. The release for production is aborted. It cannot be performed again until allcatalogs referenced by the net in question are available.

CATID x NOT CONTAINED IN LOCATION FILE

There is no entry in the assigned storage location file for the specified catalog ID. Therelease for production is aborted. The location file must be updated before the SUBMITis repeated.This message is also used if a catalog ID is neither specified in the file name nor waspassed by AVAS at the SUBMIT exit and the location file contained no entry with a blankcatalog ID, i.e. a catalog ID comprising simply four blanks.

LOCATION locname NOT ALPHANUMERIC

One of the storage locations contained in the assigned storage location file is not of the"alphanumeric" data type. The location name is possibly shorter than 8 bytes andpadded on the right with blanks.The release for production is aborted.

VALUE FOR OPERAND VOLUME NOT CORRECT

The wildcard contained a syntax error. For example, the parentheses are missing, orthe specified file version is not separated from the character string #VOL# by thecharacter "–".The release for production is aborted.

NO USERID SPECIFIED

No user ID was specified either in the file name or in the /SET-LOGON-PARAMETERScommand. Neither has AVAS passed a user ID at the SUBMIT computer center exit.The release for production is aborted.

U5184-J-Z125-7-76 277

MARENAV messages

DEVICE TYPE MISSING OR INVALID

The release for production operation was aborted for one of the following reasons:

1. A wildcard was used in connection with a device type other than a tape or acartridge.

2. An invalid device type was specified in connection with a request for scratch orprivate tapes.

FILENAME/VERSION NOT FOUND IN MAREN CATALOG

Either the file name could not be found (if (#VOL#) was specified), or the specified fileversion could not be found (if (#VOL#-nnn) was specified), or there is a discrepancy inthe DEVICE specification.The release for production is aborted.

DIFFERENT USERIDS userid1,userid2 IN MAREN CATALOG

When (#VOL#) and #UID#=*SAME were specified, tapes with different user IDs werefound in the MAREN catalog for the current file name.The release for production is aborted.

VOLUMES OF MULTI VOLUME SET ARE MISSING

When (#VOL#) is specified, it was discovered that not all VSNs of the multivolume setare entered in the MAREN catalog for the current file name.The release for production is aborted.

VOLUMES OF MULTI VOLUME HAVE DIFFERENT USERIDS

For a multivolume file, not all VSNs are assigned to the same ID in the MAREN catalog.The release for production is aborted.

FILE NOT CLOSED

On the basis of the CLOSE indicator in the archive entry for a volume, MARENAVdiscovered that when the associated file was created it was not closed, or not closedproperly. If the wildcard (#VOL#) was entered in the file assignment, the file involved isan input file, and the release for production is aborted since it would be pointless toprocess it further.If MARENAV cannot determine whether the file is an input or output file, this messagewill appear as a warning only and the release for production will proceed.

ERROR error code DURING PROCESSING OF MACRO macro name

The specified error occurred while a macro was being executed.

The release for production is aborted.

278 U5184-J-Z125-7-76

MARENAV messages

Warning messages from MARENAV

In the transport and mount listings created by MARENAV, the individual VSNs may beaccompanied by the following warnings pointing out possible sources of errors during netexecution. It is therefore advisable to check the status of the volumes indicated. Thefollowing warning messages are possible:

VOLUME EXPORTED

The specified volume has been exported and must be returned by the scheduled timeof execution.

VOLUME HAS DIFFERENT DEVICE TYPE

For the volume indicated, the device type stored in the archive entry does not match thedevice type specified in the DMS command or in the file’s TSOSCAT entry.

VOLUME CONTAINS NO VALID DATA

According to the TSOSCAT entry, no data has been written to the specified VSN, whichmust therefore not be used as an input tape.

VOLUME ONLY USED IN CASE OF RESTART

The volume is required only in the event of a restart.

U5184-J-Z125-7-76 279

7 AVAS-QUER utility routineThe AVAS-QUER utility routine reads the AVAS data stock in BS2000 and selects data forfurther processing in relational databases.

AVAS-QUER writes the data either to an output file in SQL format, or to output filescontaining the data in LOAD or CSV format. LOAD is a special INFORMIX format (see the"INFORMIX SQL" manual [4]). CSV (Comma Separated Value) is a format which can beprocessed by many database systems (e.g. by Microsoft Access).

Users must transfer the output file(s) created by AVAS-QUER to their target system (e.g.SINIX or Microsoft Windows). They then execute the files or import the data to the databasesystem.

On the target system, the user can employ suitable database queries to obtain derived infor-mation such as the following:

1. In which nets is a particular job used?

2. In which nets is a particular symbolic date (symdat) used?

3. On which days is a particular symbolic date set?

4. Dependency structures in the form:– Which net depends on another specific net?– Which net depends on the contents of a particular job variable?– Which net depends on a job in another net?– Which net tests a particular resource?– Which net depends on a particular value?

5. In which objects is a particular document used?

6. Which jobs are running on a particular PVS, or which job variable contains the PVS?

7. Which user groups use a particular calendar?

8. In which orders is a particular select turnus used?

9. For which orders or nets is there a document in the DOCLIB?

280 U5184-J-Z125-7-76

Recommended procedure AVAS-QUER utility routine

Recommended procedure

The following table shows the steps required to obtain the information listed above. Detaileddescriptions of the steps and the results can be found in the sections listed in the table.

Systemplatform

Procedure Result

BS2000 Install AVAS-QUER (see page 300) AVAS-QUER is available

Call the AVAS-QUER utility routine (seepage 300), log on to AVAS (SIGNON),create a format (CREATE-FORMAT),select objects (SELECT-OBJECT)(see page 284 and page 286)

AVAS data is read

Terminate the AVAS-QUER utility routine(see page 284)

Output files in SAM format createdby AVAS-QUER are available.They contain the selected data,which can be imported into arelational database.(see page 284)

Transfer the output file(s) created by AVAS-QUER via file transfer

Output file(s) are available ontarget system.

If INFORMIX is used as the database system:use a file transfer to transfer the fileSUXIFX.AVAS-QUER.040.CREATE-DB

File for creating an INFORMIXdatabase exists in the targetsystem.

Target systemwithdatabase(e.g. SINIXwithINFORMIX)

If INFORMIX is used as the database system:call the fileSUXIFX.AVAS-QUER.040.CREATE-DB(see page 292).If a different database is used, the databasescheme must be created by analogy with theSQL statements in the fileSUXIFX.AVAS-QUER.040.CREATE-DB.

Database and its structure (tables)are created (initialization)(see page 293 and page 294)

Call the output file(s) created by AVAS-QUER(see page 292) or import data with database-specific statements

Supply the database with values(tables are filled in)

Formulate database queries in SQL (seepage 297) or use the user interface for evalu-ation

Information on the relationships ofthe AVAS objects:in which nets is a particular job/symdat used?...

U5184-J-Z125-7-76 281

AVAS-QUER utility routine Working with AVAS-QUER

7.1 Working with AVAS-QUER

After successful installation (see page 300), the following prerequisites must be satisfied inorder to work with AVAS-QUER.

7.1.1 Prerequisites for starting AVAS-QUER

– If the assignment of the calendars to user groups is to be evaluated, the AVAS systemparameter file must be assigned with the link name $AVSSYS.

– The link name SYSLNK must be assigned to the file SYSLNK.AVAS.040

– In the system parameters of the AVAS system, the user must have COPY ELEMENTauthorization for the objects which he/she may access.

– An SDF syntax file containing the statements for AVAS-QUER must be active.

– The AVAS access processes (ZDD, ZDL) must be started.

– If INFORMIX is used as the database system, the file SUXIFX.AVAS-QUER.040.CREATE-DB must be transferred via file transfer to the target system (e.g. SINIX). Thisfile is used to create the database on the target system. Only the name of the database(avsquer) can be changed.

– To create SQL statements, AVAS-QUER requires output files in SAM format, whichmust be assigned via specific link names. Existing output files are overwritten.Depending on the desired format, AVAS-QUER expects the following link names:– INSERT FORMAT: link name $AVSQUER– LOAD FORMAT:

Name of table Link name

caltab $AVSCAL

caldaysymtab $AVSCDAY

nettab $AVSNET

netdoktab $AVSNETD

ordertab $AVSORD

orderdoktab $AVSORDD

netsymtab $AVSNETS

ordersymtab $AVSORDS

ordersturntab $AVSORDT

282 U5184-J-Z125-7-76

Working with AVAS-QUER AVAS-QUER utility routine

7.1.2 Starting AVAS-QUER

The AVAS-QUER utility routine can be called in either of two ways:

– via the procedure SYSPRC.AVAS-QUER.040:

/CALL-PROCEDURE NAME=SYSPRC.AVAS-QUER.040

– via the program SYSPRG.AVAS-QUER.040:

/START-PROGRAM FROM-FILE=SYSPRG.AVAS-QUER.040

If AVAS-QUER is called via the procedure, the link names are automatically assigned.

Structure of the procedure

/BEGIN-PROC LOG=N,PAR=YES(PROC-PAR=( -/ &SYSCMD=*PRIMARY, -/ &SYS=, -/ &AVUSERID=, -/ &AUSGABE=, -/ &FORMAT=, -/ &CAL=, -/ &CDAYSYM=, -/ &NET=, -/ &NETDOK=, -/ &ORDER=, -/ &ORDERDOK=, -/ &NETSYM=, -/ &ORDERSYM=, -/ &ORDERTUR=, -/ &SYSPAR=),ESC-CHAR=C'&')/REMARK OUTPUT FORMAT (LOAD | INSERT): &FORMAT ---------------------- (1)/SKIP-COM TO-LABEL=F&FORMAT/.FINSERT REMARK/.FI REMARK/REMARK NAME OF THE OUTPUT FILE: &AUSGABE --------------------------- (2)/SET-FILE-LINK LINK=AVSQUER,F-NAME=&AUSGABE/SKIP-COM TO-LABEL=AVUSERID/.FLOAD REMARK/.FL REMARK/REMARK NAME OF THE OUTPUT FILE FOR CALDAYSYMTAB: &CDAYSYM ---------- (2)/SET-FILE-LINK LINK=AVSCDAYS,F-NAME=&CDAYSYM/REMARK NAME OF THE OUTPUT FILE FOR NETTAB: &NET/SET-FILE-LINK LINK=AVSNET,F-NAME=&NET/REMARK NAME OF THE OUTPUT FILE FOR NETDOKTAB: &NETDOK/SET-FILE-LINK LINK=AVSNETD,F-NAME=&NETDOK/REMARK NAME OF THE OUTPUT FILE FOR ORDERTAB: &ORDER/SET-FILE-LINK LINK=AVSORD,F-NAME=&ORDER

U5184-J-Z125-7-76 283


/REMARK NAME OF THE OUTPUT FILE FOR ORDERDOKTAB: &ORDERDOK/SET-FILE-LINK LINK=AVSORDD,F-NAME=&ORDERDOK/REMARK NAME OF THE OUTPUT FILE FOR NETSYMTAB: &NETSYM/SET-FILE-LINK LINK=AVSNETS,F-NAME=&NETSYM/REMARK NAME OF THE OUTPUT FILE FOR ORDERSYMTAB: &ORDERSYM/SET-FILE-LINK LINK=AVSORDS,F-NAME=&ORDERSYM/REMARK NAME OF THE OUTPUT FILE FOR ORDERSTURNTAB: &ORDERTUR/SET-FILE-LINK LINK=$AVSORDT,F-NAME=&ORDERTUR/.AVUSERID REMARK/REMARK USER ID UNDER WHICH AVAS IS INSTALLED: &AVUSERID --------------- (3)/SET-FILE-LINK F-NAME=$&AVUSERID..SYSLNK.AVAS.040.DIALOG,LINK=SYSLNK/MODIFY-TERMINAL-OPTIONS OVERFLOW-CONTROL=NO/REMARK ASSIGN SYSTEM PARAMETER FILE (YES/NO): &SYS -------------------- (4)/SKIP-COM TO-LABEL=SYS&SYS/.SYSYES REMARK/.SYSY REMARK/REMARK NAME OF THE SYSTEM PARAMETER FILE: &SYSPAR --------------------- (5)/SET-FILE-LINK LINK=AVSSYS,F-NAME=&SYSPAR/SKIP-COM TO-LABEL=A&FORMAT/.ALOAD REMARK/.AL REMARK /REMARK NAME OF THE OUTPUT FILE FOR CALTAB: &CAL/SET-FILE-LINK LINK=AVSCAL,F-NAME=&CAL/.AINSERT REMARK/.AI REMARK/.SYSNO REMARK/.SYSN REMARK/SET-JOB-STEP/ASSIGN-SYSDTA TO-FILE=&SYSCMD/START-PROGRAM SYSPRG.AVAS-QUER.040 ----------------------------------- (6)/SET-JOB-STEP/ASSIGN-SYSDTA TO-FILE=*PRIMARY/MODIFY-TERMINAL-OPTIONS OVERFLOW-CONTROL=USER/END-PROC

(1) Specifies the format in which the output file(s) will be created.The following specifications are possible:"l" or "load": The output files are created in LOAD format."i" or "insert": The output file is created in INSERT format.

(2) Depending on the format specification, the system now queries either the name ofthe output file (in INSERT format) or the names of the output files for the individualdatabase tables (in LOAD format). The assignments to the link names are estab-lished.

(3) Specifies the user ID under which AVAS is installed.

284 U5184-J-Z125-7-76

Working with AVAS-QUER AVAS-QUER utility routine

(4) Specifies whether the system parameter file is to be assigned.The following specifications are possible:"y" or "yes": Assign the system parameter file"n" or "no": Do not assign the system parameter file

(5) If "y" ("yes") is entered for (4), the system now queries the name of the systemparameter file. AVAS-QUER is started if no system parameter file is to be assigned.

(6) AVAS-QUER is started.

7.1.3 Entering statements

Once the utility routine has been started, the AVAS-QUER statement SIGNON and thestandard SDF statements can be entered.

After SIGNON logs the user in, the CREATE-FORMAT statement is expected. Thisstatement determines the format of the output file(s) (see page 284). If CREATE-FORMATis not specified, the output data is created by default in LOAD1 format.

The user can then access the AVAS data with the AVAS-QUER statement SELECT-OBJECT to select the desired AVAS objects.

It is possible to enter the statements SIGNON and SELECT-OBJECT several times.

The statements, their syntax and operands are described from page 286 onward.

7.1.4 Terminating AVAS-QUER

The AVAS-QUER utility routine is terminated with the statement //END.

7.1.5 Structure of the output file(s) created by AVAS-QUER

An AVAS-QUER run produces a selected subset of data from the AVAS data, which can befurther processed in relational databases. This data is written to output file(s), which mustbe assigned by means of specific link names (see section “Prerequisites for starting AVAS-QUER” on page 281).

AVAS-QUER takes the following into account:

– No records are written to the output file(s) for data fields without values (*NONE,blanks). This is, for example, the case when no symdat is assigned to a calendar day.

U5184-J-Z125-7-76 285


– If the document name specified for the net description is *STD, the following names willbe entered in the "netdoktab" table:– bkdok: user group of the net– dokname: net name

– If the document name specified for the order description is *STD, the following nameswill be entered in "orderdoktab" table:– bkdok: user group of the net– dokname: netname.ordername

– All attributes of a database table are always specified in the output files. Blanks areassigned to attributes for which there are no values in the AVAS data (for example, theattribute "enterfile" in the table "ordertab" for a condition).

The user must transfer the output file(s) created in this way to the target system. There, he/she executes them or imports the data into the database. The data in the output file(s)provides values for the individual fields of the database (tables).

It is advisable to name the output files(s) with the extension ".sql".

With the AVAS-QUER statement CREATE-FORMAT, the user determines the format of thedata in the output file.

The following formats are available:

– INSERT FORMAT:Creates an output file with SQL statements with the syntax:

INSERT INTO tablename (attributename1,...)VALUES ("value for attribute1",...)

– LOAD1 format:A separate file is created for each database table. The output file records are structuredas follows:

attributevalue1|attributevalue2|....|

In this format, the data can be loaded into an INFORMIX database by means of theLOAD statement.

– LOAD2 format:A separate file is created for each database table. The output file records are structuredas follows:

"attributevalue1","attributevalue2","...."

In this format, the data can be imported directly into relational databases (such asMicrosoft Access) by means of the appropriate database-specific statements.

286 U5184-J-Z125-7-76

AVAS-QUER statements AVAS-QUER utility routine

Indicator showing availability of an assigned document in the DOCLIB

In order to determine whether a document is available in the DOCLIB, AVAS-QUERattempts to create an index for all user groups. If the user has not been given *-authorizationfor COPY-ELEMENT, AVAS-QUER will create this index only for the user’s own user group,and will output message AVSQ028.

For nets or orders to which a document has been assigned from the system user group, itis therefore impossible to determine whether the document is available. In these cases"dokvorh" (the document availability indicator in the netdoktab and orderdoktab tables) willbe set to "N".

It should be noted that in AVAS the *-authorization is only valid for libraries assigned to theuser.

7.2 AVAS-QUER statements

This section describes the AVAS-QUER statements, their syntax and operands. They aredescribed in the order in which AVAS-QUER expects them. An example follows thedescription.

Standard SDF statements

The following standard SDF statements can be entered in the course of an AVAS-QUERrun. These statements are described in the manual "Introductory Guide to the SDF DialogInterface" [10].

Standard SDF statement Meaning

END Terminate the utility routine

MODIFY-SDF-OPTIONS Modify the SDF settings

REMARK Program remarks

RESTORE-SDF-INPUT Display previous entry

SHOW-SDF-OPTIONS Display the SDF settings

STEP Define a reentry point

WRITE-TEXT Output text to SYSOUT

U5184-J-Z125-7-76 287

AVAS-QUER utility routine SIGNON

SIGNONLog in to AVAS system

The SIGNON statement is used to log in to the AVAS system. SIGNON must be the firststatement.

AVAS-USER-ID = avuserIdentifier of the AVAS user (maximum 8 characters)

PASSWORD = passwordPassword of the AVAS user (maximum 8 characters).In guided dialog, the password is not shown on the screen.

AVAS-SYSTEM-ID = stringName of the AVAS system (7 characters) with which the user wants to work.

SIGNON

AVAS-USER-ID = avuser

,PASSWORD = password

,AVAS-SYSTEM-ID = string

288 U5184-J-Z125-7-76

CREATE-FORMAT AVAS-QUER utility routine

CREATE-FORMATSelect output file format

With the CREATE-FORMAT statement, the user selects the format for the output file(s) tobe created. CREATE-FORMAT is expected as the second statement (after SIGNON). Ifspecified after SELECT-OBJECT, CREATE-FORMAT is ignored. If CREATE-FORMAT isnot specified, the format LOAD1 is used by default.

FORMAT-NAME =Specifies the format of the output file (see page 284).

FORMAT-NAME = INSERTThe output file contains the AVAS data in SQL INSERT statements.

FORMAT-NAME = LOAD1The output file contains the AVAS data in INFORMIX LOAD format.

FORMAT-NAME = LOAD2The output files contains the AVAS data in the general LOAD format.

CREATE-FORMAT

FORMAT-NAME = INSERT | LOAD1 | LOAD2

U5184-J-Z125-7-76 289

AVAS-QUER utility routine SELECT-OBJECT

SELECT-OBJECTSelect AVAS objects

With the SELECT-OBJECT statement, the user selects AVAS objects for processing. Theuser must have COPY ELEMENT authorization for these objects.

Note:

If an AVAS element is selected several times (either by direct specification of its nameor by partially qualified specifications), it will be written to the output file several times.This is also true for system parameters, if SYSTEM-PARAMS=[*]YES is specified.

NET-NAME =Specifies whether AVAS nets are to be selected.

NET-NAME = *NONo AVAS nets are to be selected.

NET-NAME = netnameName of the AVAS net (written as [$ug_]netname) used to select the objects. The netdescription is entered in the net library under this name.The net name can also be specified in partially qualified form (see section “Naming conven-tions” on page 42).

CALENDAR-NAME =Specifies whether AVAS calendars are to be selected.

CALENDAR-NAME = *NONo AVAS calendars are to be selected.

CALENDAR-NAME = calendarName of the AVAS calendar to be selected. The calendar description is entered in thecalendar library under this name. The calendar name can also be specified in partiallyqualified form (see section “Naming conventions” on page 42).

SELECT-OBJECT

NET-NAME = *NO | netname

,CALENDAR-NAME = *NO | calendar

,SYSTEM-PARAMS = [*]NO | [*]YES

290 U5184-J-Z125-7-76

SELECT-OBJECT AVAS-QUER utility routine

SYSTEM-PARAMS =Specifies whether the assignment of calendars to user groups is to be selected from theAVAS system parameters.

SYSTEM-PARAMS = *NOThe assignment of calendars to user groups is not to be copied.

SYSTEM-PARAMS = *YESThe assignment of calendars to user groups is to be copied from the system parameter fileinto the output file.

Example

The AVAS-QUER utility routine is called via the procedure. The output file "output" is to becreated in INSERT format. It is then to be made available in the SINIX system with the name"insert.sql".

/CALL-PROCEDURE NAME=SYSPRC.AVAS-QUER.040 ------------------------------- (1)%/REMARK OUTPUT FORMAT (LOAD | INSERT): &FORMAT%&FORMAT=insert --------------------------------------------------------- (2)%/REMARK NAME OF THE OUTPUT FILE: %VERSION%&AUSGABE=output -------------------------------------------------------- (3)%/REMARK USER ID UNDER WHICH AVAS IS INSTALLED: &AVUSERID%&AVUSERID=avasuid1 ----------------------------------------------------- (4)%/REMARK ASSIGN SYSTEM PARAMETER FILE (YES/NO): &SYS%&SYS=yes --------------------------------------------------------------- (5)%/REMARK NAME OF THE SYSTEM PARAMETER FILE: &SYSPAR%&SYSPAR=$avasuid1.avas.040.user.syspar --------------------------------- (6)% BLS0500 PROGRAM 'AVAS-QUER', VERSION 'V3.0A00' OF '1994-12-15' LOADED% BLS0552 COPYRIGHT (C) SIEMENS NIXDORF INFORMATIONSSYSTEME AG 1994. ALLRIGHTS RESERVED --------------------------------------------------------- (7)//signon avas-user-id=quer,password=quer1,avas-system=avas030 ----------- (8)% AVS2201 START 'AVAS-QUE'; 'V3.0A00'//create-format format-name=insert -------------------------------------- (9)//select-object net-name=net001,calendar-name=examp*, -// system-params=yes --------------------------------------------- (10)/end ------------------------------------------------------------------- (11)

in the target system (here SINIX:)

$ ncopy <partnerrechner>!output insert.sql <userid,acc,password> ------- (12)ncopy: Receive request insert.sql(07997) startedncopy: Receive request insert.sql(07997) completed$ isql ----------------------------------------------------------------- (13)

(1) Starts the procedure

(2) Specifies the desired format

U5184-J-Z125-7-76 291

AVAS-QUER utility routine SELECT-OBJECT

(3) Name of the output file to be created

(4) Specifies the user ID

(5) Specifies whether a system parameter file is to be assigned

(6) Specifies the name of the system parameter file

(7) Call AVAS-QUER

(8) Log in to AVAS-QUER via SIGNON

(9) Specify the format for the output file

(10) Select objects

(11) Terminate AVAS-QUER

(12) In the target system:Fetch and simultaneously rename the output file "output" created by AVAS-QUER.The partner computer and the access authorizations for the partner computer mustbe entered in the ncopy command. The password is entered without quotes. Afterthe ncopy command is terminated, the file is available in the target system with thename "insert.sql". INFORMIX requires the extension ".sql" as a criterion for filehandling.The file SUXIFX.AVAS-QUER.040.CREATE-DB must also have been loaded on thetarget system and the database created using it. Only when this has been done canthe output file which is created be loaded into the database.

(13) The INFORMIX database program is called with "isql".The database-specific commands and statements can then be entered:– INFORMIX-SQL: ..... SQL-Dialog .....

Conduct an interactive dialog using SQL statements.– SELECTION DATABASE >> avsquer

Select a database or enter names. Continue with RETURN.– SQL-Dialog: . . . . . . File .

Load, save or delete a statement file.– FILE: Load ....

Read in a dialog statement from a statement file.– SELECTION >> insert

Select a statement file or enter the name. Continue with RETURN.– SQL-Dialog: . START . . . . . .

Execute a dialog statement.– SQL-Dialog: New . . . . . . .

Enter a new dialog statement.– SQL-Dialog: . START . . . . . .

Execute a dialog statement.– ...

292 U5184-J-Z125-7-76

Data storage for AVAS-QUER AVAS-QUER utility routine

7.3 Data storage for AVAS-QUER

7.3.1 Creating the database

If INFORMIX is used as the database system, the user must transfer the file SUXIFX.AVAS-QUER.040.CREATE-DB (supplied with AVAS-QUER) to the desired target system via filetransfer, and must execute it there. This file contains SQL statements for creating tables.The relationships of the AVAS objects are subsequently stored in these tables.

The database used to create these statements is called "avsquer". This name can bemodified by the user. The name of the database is contained in the first two lines of the file:

CREATE DATABASE avsquer; DATABASE avsquer;

The user cannot modify the subsequent statements for creating the database tables.

The SQL statements can be executed, for example, with INFORMIX isql (SQL dialog menu,items File and START). The item File prompts isql to list the files with an ".sql" extension,for the user to make a selection .

7.3.2 Importing the data

The user must transfer the output file(s) created by AVAS-QUER to the desired targetsystem via file transfer.

Importing the data into the INFORMIX database

INSERT FORMAT:The SQL statements can be executed, for example, with INFORMIX isql (SQL dialog menuitems, File, Load and START).

LOAD1 FORMAT:The data can be loaded into the database with INFORMIX isql by the SQL statement LOAD(SQL dialog menu, New) and the statementLOAD-FROM filename INSERT INTO tablename [START]

Importing the data into other databases

This concerns the output files created in LOAD2 format.

Depending on the database system used, it may be necessary to define the databasetables beforehand. The data is entered in the database with the database-specific state-ments. The user must modify the output files created by AVAS-QUER if his/her databasesystem supports another format.

U5184-J-Z125-7-76 293

AVAS-QUER utility routine Data storage for AVAS-QUER

7.3.3 Structure of the database

figure 2 illustrates the structure of the database with its tables. The AVAS objects and theirrelationships (cross-references) are stored in these tables.

The structural elements of a net are called "orders"

Structure of the database in the target system

User group

Calendar

Calendarday

Structureelement

Document

Net

ordertab

nettab

ordersymtab orderdoktab

netdoktab

caltab

netsymtabcaldaysymtab

Table nameTables in the database

ordersturntab

Select turnus

Symdat

294 U5184-J-Z125-7-76


7.3.4 Structure of the database tables

caltab

The caltab table contains the assignment of calendars to user groups.

caldaysymtab

The caldaysymtab table contains the assignment of symdats to calendar days.

nettab

The nettab table contains the assignment of PVSs to nets.

netdoktab

The netdoktab table contains the assignment of documents to nets.

bkcal char(4) Name of user group

calname char(20) Calendar name

calname char(20) Calendar name

datum char(8) Date of the calendar day (YYYYMMDD)

symdat char(20) Name of the symbolic date (symdat)

bknet char(4) User group of the net

netname char(12) Net name

pvs char(54) Assigned PVS or job variable name



bkdok char(4) User group of the document

dokname char(37) Document name

dokvorh char(1) Indicator (Y/N), showing whether the document is availablein the DOCLIB.

U5184-J-Z125-7-76 295


ordertab

The ordertab table contains the assignment of pubsets to jobs and the assignment of jobsto nets, plus the dependencies on any nets, jobs, condition values, resources or jobvariables.

orderdoktab

The orderdoktab table contains the assignment of documents to structure elements.



indexnr char(3) Index level

bkorder char(4) User group of the structure element. If no user group isspecified for a JOB or NET condition, the user group of thenet is entered.

ordername char(24) Structure element name.

function char(1) Structure element function (FU):J/P/X (job, S procedure, server job), P (S procedure),C (compare), W (wait), M (modify), D (delete), A (add)

typ char(3) Structure element type:Condition NET, JOB, VAL, RES, JVA,Job type MOD, STD, EXT, EXX, TIM.

pvs char(54) Pubset assigned to the job, or job variable containing thepubset. Pubset is written in quotes to distinguish betweenpubset and JV (for function=J/P/X)

jvname char(54) Name of the job variable for type=JVA

enterfile char(54) Name of the enter file for type=EXT

cond_index char(3) Index level of the job on which there is a dependency(for type=JOB)

cond_bknet char(4) User group of the net on which there is a dependency(for type=JOB or NET). If no user group is specified, that ofthe net itself will be recorded here.

cond_netname char(24) Name of the net on which there is a dependency




bkorder char(4) User group of the order

296 U5184-J-Z125-7-76


netsymtab

The netsymtab table contains the assignment of symdats to nets.

ordersymtab

The ordersymtab table contains the assignment of symdats to structure elements.

ordersturntab

The ordersturntab table contains the assignment of selectturnus to structure elements.

ordername char(24) Name of the structure element

bkdok char(4) User group of the document

dokname char(37) Document name

dokvorh char(1) Indicator (J/N), showing whether the document is presentin the DOCLIB.



symdat char(20) Name of the symbolic date (Symdat) with relative specifica-tions (+/- nn: 1<nn<99)

starttime char(6) Symbolic name of the start time

lateststart char(7) Symbolic name of the latest start time




bkorder char(4) User group of the structure element


symdat char(20) Name of the symbolic date (symdat)




bkorder char(4) User group of the structure element


selectturnus char(1) Select turnus

U5184-J-Z125-7-76 297


7.3.5 Sample database queries

The following examples illustrate which SQL instructions the user must issue in the targetsystem in order to obtain the information listed on page 279.

1. In which nets is a particular job used?

Examples:

– In which nets is the job "$QUER_JOB1" used?

SELECT bknet,netname FROM ordertab WHERE (ordername="JOB1" AND bkorder="QUER" AND function="J")

– In which net descriptions is the symbolic date "SYMDATE10" used?

SELECT bknet,netname FROM netsymtab WHERE symdat="SYMDATE10"

– In which orders is the symbolic date "SYMDATE1" used?

SELECT bknet,netname,ordername FROM ordersymtab WHERE symdat="SYMDATE1"

– In which jobs is the symbolic date "SYMDATE1" used?

SELECT DISTINCT os.bknet,os.netname,os.ordername FROM ordersymtab os, ordertab o WHERE (os.symdat="SYMDATE1" AND (o.bknet=os.bknet AND o.netname=os.netname AND o.ordername=os.ordername AND o.function="J"))

2. In which nets is a particular symbolic date used?

Example:

In which nets is the symbolic date "SYMDATE10" used?

SELECT bknet,netname FROM netsymtab WHERE symdat="SYMDATE10" UNIONSELECT bknet,netname FROM ordersymtab WHERE symdat="SYMDATE10"

3. On which days is a particular symbolic date set?

Example:

On which days is the symbolic date "SYM1" set?

SELECT calname,date FROM caldaysymtab WHERE (symdat="SYM1")

298 U5184-J-Z125-7-76


4. Which net depends on another specific net or on the contents of a particular job variable(dependency structures)?

Examples:

– Which nets depend on the net "$QUER_NET1"?

SELECT bknet,netname FROM ordertab WHERE (ordername="NET1" AND bkorder="QUER" AND typ="NET" AND function="C")

– Which nets depend on the job variable "JVA1"?

SELECT bknet,netname FROM ordertab WHERE (ordername="JVA1" AND typ="JVA" AND function="C")

– In which nets is there a dependency on "JOB1" in the net "$QUER-NET1"?

SELECT bknet,netname FROM ordertab WHERE (ordername="JOB1" AND typ="JOB" AND function="C" AND cond_bknet="QUER" AND cond_netname="NET1")

– In which nets is there a dependency on the resource "RES10"?

SELECT bknet,netname FROM ordertab WHERE (ordername="RES10" ANDtyp="RES" AND function="C")

– Which nets modify the entry for the resource "RES1"?

SELECT bknet,netname FROM ordertab WHERE (ordername="RES1" ANDfunction="M" AND typ="RES")

– To which net descriptions is the document "$QUER_DOCUMENT1" assigned?

SELECT bknet,netname FROM netdoktab WHERE (bkdok="QUER" AND dokname="DOCUMENT1")

5. In which objects is a particular document used?

Examples:

– To which nets is the document "$QUER_DOCUMENT1" assigned?

SELECT bknet,netname FROM netdoktab WHERE (bkdok="QUER" AND dokname="DOCUMENT1") UNIONSELECT bknet,netname FROM orderdoktab WHERE (bkdok="QUER" AND dokname="DOCUMENT1")

– In which nets is the pubset "ABCD" used?

SELECT bknet,netname FROM nettab WHERE pvs="'ABCD'" UNIONSELECT bknet,netname FROM ordertab WHERE pvs="'ABCD'"

– In which jobs is the pubset "ABCD" used?

SELECT bknet,netname,ordername FROM ordertab WHERE pvs="'ABCD'"

U5184-J-Z125-7-76 299


6. Which jobs are running on a particular pubset, or which job variable contains thepubset?

Example:

Which jobs are running on the pubset "ABCD"?

SELECT DISTINCT o.bknet,o.netname,o.ordername FROM ordertab o, nettab n WHERE (o.pvs="'ABCD'" OR (o.bknet=n.bknet AND o.netname=n.netname AND n.pvs="'ABCD'" AND o.function="J"))

7. Which user group is using a particular calendar?

Example:

Which user groups are using the calendar "EXAMPLECALENDAR"?

SELECT bkcal FROM caltab WHERE (calname="EXAMPLECALENDAR")

8. In which orders is a particular selectturnus used?

Example:

In which orders is selectturnus 7 used?

SELECT bknet,netname,ordername FROM ordersturntab WHERE (selectturnus="7")

9. For which orders or nets is there a document in the DOCLIB and what is its name?

Example:

SELECT bknet,netname,bkorder,bkdoc,dokname FROM orderdoctab WHERE (docvorh="y")

300 U5184-J-Z125-7-76

Error handling AVAS-QUER utility routine

7.4 Error handling

Successful login with SIGNON is necessary in order to process the SELECT-OBJECTstatement. If this is not the case, all SELECT-OBJECT statements will be ignored until thenext SIGNON or END statement.

If an error occurs when output file(s) are opened, the program is terminated.

If it is not possible to write to the output file(s), processing of the SELECT-OBJECTstatement is aborted and the program is terminated.

If the user accesses an object locked by AVAS while processing AVAS objects, a messageis issued and processing continues with the next object.

The user is informed of all errors by messages and the corresponding error information.

Syntactically incorrect net names ($ABCDEF.ABC,..) are rejected with message AVSQ017(if a fully qualified object name was specified), or with message AVSQ013 or AVSQ021 (ifa partially qualified object name was specified).

Temporary files

While AVAS-QUER is running, temporary files are created in BS2000.

If an error occurs during processing, the temporary files may not be deleted. The user mustthen delete these files.

The following temporary files are created:

for the contents list: $<userid>.AVAS-QUER.tsn.yyyy-mm-dd.hhmmssfor the AVAS objects: $<userid>.AVAS-QUER.tsn.objectname

7.5 Installation

Software dependencies

The following products are required in order to execute AVAS-QUER:

– BS2000/OSD V1.0 or higher– SDF-A V2.0A or higher– AVAS V4.0A– file transfer to transfer the file to the target system with SQL statements– database system (e.g. INFORMIX)

U5184-J-Z125-7-76 301

AVAS-QUER utility routine Installation

Components for installation

The following components are supplied for AVAS-QUER:

The files must be copied to the desired user ID.

Installing the syntax file

The system syntax file supplied (SYSSDF.AVAS-QUER.040.SYSTEM) can be merged withthe current system syntax file with the "SDF-I" utility routine (see the manual "SDFManagement" [11]).

Alternatively, the user syntax file, SYSSDF.AVAS-QUER.040.USER can be activated by thecommand /MODIFY-SDF-OPTIONS SYNTAX-FILE=SYSSDF.AVAS-QUER.040.USER.

Assigning the report file

The messages and help texts must be created from the complete primary message fileSYSMSV.AVAS-QUER.040.

The MSGLIB utility routine creates the following files from the primary message file (see the"Utility Routines" manual [12]):– a message output file SYSMSA.AVAS-QUER.040 (type MSG) and– a reduced primary message file SYSMSR.AVAS-QUER.040 (type HELP)

The message output file is activated with the command MODIFY-MSG-FILE-ASSIGNMENT.

Component Purpose

SYSPRC.AVAS-QUER.040 Procedure for starting AVAS-QUER

SYSMSV.AVAS-QUER.040 Primary message file

SYSSDF.AVAS-QUER.040.SYSTEM System syntax file

SYSSDF.AVAS-QUER.040.USER User syntax file

SYSPRG.AVAS-QUER.040 Program file

SUXIFX.AVAS-QUER.040.CREATE-DB File for creating an INFORMIX database

302 U5184-J-Z125-7-76

AVAS-QUER messages AVAS-QUER utility routine

7.6 AVAS-QUER messages

AVSQ001 INVALID OPERAND ’(&00)’

MeaningAVAS-USERID: The user has not been included in the AVAS system parametersAVAS-SYSTEM-ID:

- the specified AVAS system identification is invalid- the access tasks of the system identification have not been loadedIf necessary, inform the AVAS administrator.

PASSWORD: The specified password is invalid.

AVSQ002 REQM MAKRO ERROR ’(&00)’

AVSQ003 SDF NOT AVAILABLE

AVSQ004 RDSTMT MAKRO ERROR ’(&00)’ WHEN READING A STATEMENT.

AVSQ005 DMS ERROR ’(&01)’ WHEN CLOSING FILE ’(&00)’. IN SYSTEM MODE /HELP-MSG DMS(&01)

MeaningFor more detailed information about DMS error codes enter /HELP-MSG DMS(&01) insystem mode or see the DMS manual.

AVSQ006 SIGNOFF ERROR

AVSQ007 AVAS ERROR ’(&00)’ DURING SIGNON PROCESSING. IN SYSTEM MODE /HELP-MSG AVS(&00)

MeaningFor more detailed information about AVAS error codes enter /HELP-MSG AVS(&00) insystem mode or see manual "AVAS for the User".

AVSQ008 DMS ERROR ’(&00)’ WHEN OPENING OUTPUT FILE. IN SYSTEM MODE /HELP-MSG DMS(&00)


AVSQ009 DMS ERROR ’(&01)’ WHEN OPENING FILE ’(&00)’. IN SYSTEM MODE /HELP-MSG DMS(&01)


AVSQ010 DMS ERROR ’(&01)’ WHEN READING FILE ’(&00)’. IN SYSTEM MODE /HELP-MSG DMS(&01)


U5184-J-Z125-7-76 303

AVAS-QUER utility routine AVSQ011

AVSQ011 AVAS-ELEMENT ’(&00)’ CURRENTLY LOCKED

AVSQ012 INTERNAL ERROR ’(&00)’ WHEN READING AN AVAS-ELEMENT. AVAS-RETURNCODE: AVS(&01)

Meaning(&00) internal AVAS-QUER error codePass the error message to the AVAS-QUER engineers.

AVSQ013 AVAS ERROR ’(&00)’ WHEN READING AN AVAS-ELEMENT. IN SYSTEM MODE /HELP-MSGAVS(&00)

MeaningFor more detailed information about AVAS error codes enter /HELP-MSG AVS(&00) insystem mode or see the manual "AVAS for the User".

AVSQ014 DMS ERROR ’(&00)’ WHEN WRITING OUTPUT FILE. IN SYSTEM MODE /HELP-MSG DMS(&00)


AVSQ015 ERASE MAKRO ERROR ’(&01)’ WHEN DELETING FILE ’(&00)’.

AVSQ016 DMS ERROR ’(&00)’ WHEN CLOSING OUTPUT FILE. IN SYSTEM MODE /HELP-MSG DMS(&00)

MeaningFor more detailed information about DMS error codes enter /HELP-MSG DMS(&00) or seethe DMS manual.

AVSQ017 AVAS-ELEMENT ’(&00)’ NOT FOUND.

AVSQ018 DMS ERROR ’(&00)’ WHEN OPENING SYSTEM PARAMETER FILE. IN SYSTEM MODE /HELP-MSGDMS(&00)

MeaningFor more detailed information about DMS error codes enter /HELP-MSG DMS(&00) insystem mode or see DMS manual.

AVSQ019 DMS ERROR ’(&00)’ WHEN CLOSING SYSTEM PARAMETER FILE. IN SYSTEM MODE /HELP-MSGDMS(&00)


AVSQ020 COMMAND COPY-ELEMENT NOT ALLOWED.

MeaningThere is no authorization to use COPY-ELEMENT in the AVAS-USERS function table, orthe necessary AVAS access tasks have not been loaded

304 U5184-J-Z125-7-76

AVSQ021 AVAS-QUER utility routine

AVSQ021 NO AVAS-ELEMENT ’(&00)’ FOUND.

AVSQ022 FILE MAKRO ERROR ’(&00)’

AVSQ023 RDTFT MAKRO ERROR ’(&00)’

AVSQ024 LOAD LIBRARY ’SYSLNK.AVAS.040’ NOT SPECIFIED

AVSQ025 STATEMENT ’//CREATE-FORMAT’ IGNORED

AVSQ026 JINF MAKRO ERROR ’(&00)’

AVSQ027 DMS-ERROR ’(&00)’ WHEN CLOSING DOCUMENT FILE. IN SYSTEM MODE /HELP-MSG DMS(&00)

AVSQ028 DOCUMENT FILE CREATED FOR OWN USER GROUP

AVSQ029 DMS-ERROR ’(&00)’ WHEN OPENING DOCUMENT FILE. IN SYSTEM MODE /HELP-MSG DMS(&00)

AVSQ030 DMS-ERROR ’(&00)’ WHEN READING DOCUMENT FILE. IN SYSTEM MODE /HELP-MSG DMS(&00)

U5184-J-Z125-7-76 305

8 Masks for job managementThe system masks in AVAS have six-character names, beginning with the letters AV andfollowed by an alphabetical group identifier and a three-digit serial number.The system masks are also arranged in alphabetical order, in accordance with the groupidentifier.

Overview

AVC... Masks for calendar functions

AVC001 Set up a calendarAVC002 Display a calendar for modificationAVC004 Display the parameters of a calendar dayAVC010 Overview of calendarsAVC012 Copy calendars

AVD... Masks for condition descriptions

AVD030 Display parameters of a condition descriptionAVD031 Display users of a condition descriptionAVD040 Overview of condition descriptions

AVE... Masks for editing jobs, S procedures, server jobs and JCL elements

AVE010 Overview of jobs, S procedures, server jobs and JCL elementsAVE011 Output after termination of EDT

AVI... Masks for current information

AVI015 Overview of user masks

306 U5184-J-Z125-7-76

System masks

AVN... Masks for net editing

AVN001 Parameters for the net control recordAVN002 Parameters for control records with FU=J/PAVN003 Parameters for control records with FU=C and TYPE=JVAAVN004 Overview of control records for a netAVN005 Display a net description for copyingAVN006 Parameters for defining net masksAVN007 Parameters of the net description for modificationAVN008 Parameters of control records with FU=C and TYPE=NET/JOB/RES/VALAVN009 Parameter of a structure element with FU=XAVN011 Overview of net descriptionsAVN012 Overview of net descriptions for copyingAVN020 Plan data of a netAVN021 Plan data of a control record with FU=J/P/XAVN022 Plan data of a control record with FU=CAVN023 Plan data of a control record with FU=WAVN024 Plan data of a control record with FU=A/M/D and TYPE=RES/VAL or with

FU=D and TYPE=NET/JOBAVN030 Parameters of a control record with FU=A/M/D and TYPE=RES/VALAVN031 Parameters of a control record with FU=D and TYPE=NET/JOBAVN032 Parameters of a control record with FU=W and TYPE=TIM

AVS... Masks for system dialog

AVS010 AVAS signonAVS011 Input/output AVAS library elementsAVS015 Mask for entry of print parametersAVS016 Output after editing of documentation elementsAVS019 Overview of documentation elementsAVS020 Overview of AVAS functionsAVS025 Display the HELP text for an AVAS functionAVS030 Empty mask

Note

Mask names of up to 8 characters in accordance with FHS conventions can be used foruser masks. The character string AVM$xxxx is reserved for AVAS system masks.

U5184-J-Z125-7-76 307

System masks AVC001/002

The parameter fields for mask AVC001 are described on page 239 onwards.


AVAS-Vnn.yxmm/AVC001 C A L E N D A R - H A N D L I N G dd.mm.yy/hh:mm:ss

CALENDAR-NAME = SYMDAT-NAME = FIRST-CALENDAR-DATE = DD.MM.YY LAST-CALENDAR-DATE = DD.MM.YY

TYPE OF THE DAY ( WORK / NWRK / FREE ): MON= TUE= WED= THU= FRI= SAT= SUN= SPECIAL NWRK OR FREE DATES = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = SYSTEM-SYMDAT-NAMES: LAST WORKING DAY OF THE MONTH EVERY DAY DAY OF THE MONTH EVERY WORKING DAY WORKING DAY OF THE MONTH

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVC002 C A L E N D A R - H A N D L I N G dd.mm.yy/hh:mm:ss CAL-NAME= FIRST-CAL-DATE= LAST-CAL-DATE=

M DATE DAY TYPE SYMDATE

LINES/DAY= FROM-DATE= TO-DATE= NEXT= COPY-TO-CAL-DATE= COPY-FROM-CALENDAR=CMD: OPR:

MSG:

308 U5184-J-Z125-7-76

AVC004/010 System masks



AVAS-Vnn.yxmm/AVC004 C A L E N D A R - H A N D L I N G dd.mm.yy/hh:mm:ss CAL-NAME= FIRST-CAL-DATE= LAST-CAL-DATE=

DATE = DAY= TYPE=

SYMDATE

ENTER CONTINUE FOR UPDATE OR IGNORE FOR NO-UPDATE

CMD: OPR:

MSG:


M CALENDAR-NAME DATE RESULT

CMD: OPR:

MSG:

U5184-J-Z125-7-76 309

System masks AVC012/020


The parameter fields for mask AVC020 are described in “AVAS Job Handling“ [2].


M CALENDAR-NAME DATE COPY-CALENDAR-NAME OVER- RESULT WRITE

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVC020 P E R I O D - H A N D L I N G dd.mm.yy/hh:mm:ss

PERIOD-NAME= TYPE=

DD.MM.YY HH:MM

PERIOD-START-DATE= PERIOD-START-TIME=

PERIOD-END-DATE = PERIOD-END-TIME =

CMD: OPR:

MSG:

310 U5184-J-Z125-7-76

AVC021 System masks

The parameter fields for mask AVC021 are described in “AVAS Job Handling“ [2].

AVAS-Vnn.yxmm/AVC021 P E R I O D - H A N D L I N G dd.mm.yy/hh:mm:ss

M PERIOD-NAME TYPE P-S-DATE P-S-TIME P-E-DATE P-E-TIME RESULT DD.MM.YY HH:MM DD.MM.YY HH:MM

CMD: OPR:

MSG:

U5184-J-Z125-7-76 311

System masks AVD001/002

The parameter fields for mask AVD001 are described in "AVAS Job Handling" [2].


AVAS-Vnn.yxmm/AVD001 M O D I F Y - S U B M I T T E D - N E T dd.mm.yy/hh:mm:ss NET-PARAMETER NET-NAME= NET-STATUS= NET-TEXT=

EARLIEST-START= / PLAN-START = / LATEST-START = / NET-DELAY-SOLUTION =

RUN-CONTROL-SYSTEM = OPERATOR-START =

NET-TYPE = NET-CAT = NET-USER = NET-ACCOUNT = NET-PASSWORD= NET-CLASS = NET-LOG =

NET-PARAMETER=

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVD002 M O D I F Y - S U B M I T T E D - N E T dd.mm.yy/hh:mm:ss JOB-PARAMETER NET-NAME = NET-STATUS= JOB-NAME = JOB-STATUS= JOB-INDEX = FU= JOB-TYPE = SYNC-INDEX = RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3 LATEST-START = / DELAY-SOLUTION= ENTER-PARAMS =

JOB-CAT = USER = JOB-ACCOUNT = PASSWORD= JOB-CLASS = LOG = JOB-PARAMETER=

ENTER-FILE = FILE-PASSWORD=

CMD: OPR:

MSG:

312 U5184-J-Z125-7-76

AVD003/004 System masks



AVAS-Vnn.yxmm/AVD003 M O D I F Y - S U B M I T T E D - N E T dd.mm.yy/hh:mm:ss CONDITION-PARAMETER NET-NAME = NET-STATUS=

COND-NAME = COND-STATUS= COND-INDEX = FU= COND-TYPE = SYNC-INDEX =

RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3

LATEST-OCCURE= / DELAY-SOLUTION=

COND-JVA-NAME= JVA-POSITION = JVA-LENGTH= JVA-PASSWORD= COND-VALUE =

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVD004 M O D I F Y - SUBMITTED - NET / - JOB dd.mm.yy/hh:mm:ss NET-NAME = NET-STATUS= NET-TEXT=

M IND F TYP NAME STATUS SYN RESTART-IND RESULT IND V1 V2 V3

CMD: OPR:

MSG:

U5184-J-Z125-7-76 313




AVAS-Vnn.yxmm/AVD005 R E S T A R T - N E T dd.mm.yy/hh:mm:ss NET-NAME= NET-STATUS= NET-TEXT=

POINT-OF-ERROR: ERROR-INDEX= -NAME= RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3

POINT-OF-RESTART: SELECT-RESTART-VARIANT= M IND FU TYPE NAME SYN-IND STATUS

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVD006 M O D I F Y - S U B M I T - J O B dd.mm.yy/hh:mm:ss JOB-PARAMETER NET-NAME = NET-STATUS= JOB-NAME = JOB-STATUS= JOB-INDEX = FU= JOB-TYPE = SYNC-INDEX = RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3 LATEST-START = / DELAY-SOLUTION= ENTER-PARAMS =

ENTER OPERATION:SAVE FOR UPDATE OR OPERATION:RETURN FOR NO-UPDATE

CMD: OPR:

MSG:

314 U5184-J-Z125-7-76


The parameter fields for mask AVD007 are described in “AVAS Job Handling“ [2].


AVAS-Vnn.yxmm/AVD007 N E T - S T R U C T U R E dd.mm.yy/hh:mm:ss

NET-NAME= NET-STATUS= EARLIEST-START= / NEW-START = / MODIFY-LATEST=

M IND F NAME STATUS R SYN- RESTART-IND RESULT V IND V1 V2 V3

SELECT-RESTART-VARIANT=CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVD008 N E T - S T R U C T U R E dd.mm.yy/hh:mm:ss

NET-NAME= NET-STATUS= EARLIEST-START= / NEW-START = / MODIFY-LATEST=

M IND FU TYPE NAME SYN-IND STATUS RESULT

CMD: OPR:

MSG:

U5184-J-Z125-7-76 315




AVAS-Vnn.yxmm/AVD009 M O D I F Y - S U B M I T T E D - NET dd.mm.yy/hh:mm:ss CONDITION-PARAMETER NET-NAME = NET-STATUS=




CONDITION CREATED BY: NET-NAME= INDEX= OCCURE-VALUE =

ERROR-VALUE =


MSG:




COND-VALUE =

CMD: OPR:

MSG:

316 U5184-J-Z125-7-76




AVAS-Vnn.yxmm/AVD011 L I S T O F SUBMITTED N E T S dd.mm.yy/hh:mm:ss

RUN-CONTROL-SYSTEM=

M NET-NAME IND NET-STATUS/CALLED FOR RESULT OBJ

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVD012 R E S T A R T - N E T dd.mm.yy/hh:mm:ss LIST OF NETS WITH STATUS ERRORM NET-NAME ERR-IND EARLIEST-START NET-STATUS/CALLED FOR REST-VAR -IND MODIFY-LATEST NEW-START RESULT / / / / / / / / / / / / / /

FROM-DATE= / TO-DATE= /

CMD: OPR:

MSG:

U5184-J-Z125-7-76 317




AVAS-Vnn.yxmm/AVD015 L I S T O F SUBMITTED N E T S dd.mm.yy/hh:mm:ss

M NET-NAME IND EARLIEST-START NET-STATUS/CALLED FOR MODIFY-LATEST NEW-START RESULT / / / / / / / / / / / / / /

FROM-DATE= / TO-DATE= /

CMD: OPR:

MSG:




CONDITION CREATED BY: NET-NAME= INDEX=

CMD: OPR:

MSG:

318 U5184-J-Z125-7-76







DATE = TIME =

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVD018 M O D I F Y - S U B M I T T E D - NET dd.mm.yy/hh:mm:ss SERVER-JOB-PARAMETER NET-NAME = NET-STATUS= JOB-NAME = JOB-STATUS= JOB-INDEX = FU= JOB-TYPE = SYNC-INDEX = RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3 LATEST-START = / DELAY-SOLUTION= ENTER-PARAMS =

JOB-CAT = USER = JOB-ACCOUNT = PASSWORD= JOB-CLASS = LOG = JOB-PARAMETER=

SERVER-NAME= SERVER-PASSWORD= FILENAME =

CMD: OPR:

MSG:

U5184-J-Z125-7-76 319

System masks AVD030/AVD031

The parameter fields for mask AVD030 are described on page 215 onwards.

The parameter fields for mask AVD031 are described on page 224 onwards.

AVAS-Vnn.yxmm/AVD030 CONDITION-DESCRIPTION dd.mm.yy/hh:mm:ss

COND-TYPE = COND-STATUS = COND-NAME = CREATED BY = INDEX= CREATION DATE= /

COND-TEXT =

COND-DOC =

LIFE-TIME = / LAST-UPDATE = /

VALUE-FORMAT = COND-VALUE =

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVD031 CONDITION-USER dd.mm.yy/hh:mm:ss

COND-TYPE = COND-STATUS= COND-NAME = CREATED BY = INDEX=

M NET-NAME/USER INDEX DATE/TIME WAITING/USING OCCURE-VALUE /

/

/

/

CMD: OPR:

MSG:

320 U5184-J-Z125-7-76

AVD040 System masks

The parameter fields for mask AVD040 are described on page 220.

AVAS-Vnn.yxmm/AVD040 SHOW/MODIFY/DELETE-COND-DES dd.mm.yy/hh:mm:ss

M TYPE CONDITION-NAME OBJ STATUS RESULT CREATED BY NET-NAME / USER IND

CMD: OPR:

MSG:

U5184-J-Z125-7-76 321

System masks AVE010/011

The parameter fields for mask AVE010 are described on page 97 onwards.

The parameter fields for mask AVE011 are described on page 98 onwards.

AVAS-Vnn.yxmm/AVE010 EDIT- / SHOW- / DELETE-(PROD)JOB dd.mm.yy/hh:mm:ss AVAS-USER-LIBRARY=M F ELEMENT-NAME DATE RESULT

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVE011 EDIT- / SHOW- (PROD) JOB dd.mm.yy/hh:mm:ss AVAS-USER-LIBRARY=

ELEMENT-NAME =

NEW-ELEMENT-NAME=

OVERWRITE=

FUNCTION = J - JOB P - PROCEDURE

CMD: OPR:

MSG:

322 U5184-J-Z125-7-76

AVF001/002 System masks

The parameter fields for mask AVF001 are described in "AVAS Job Handling" [2].


AVAS-Vnn.yxmm/AVF001 S U B M I T / R E P E A T - N E T dd.mm.yy/hh:mm:ss

M NET-NAME EARLIEST-START IND RESULT OBJ / / / / / / / / / / / / / / / FROM-DATE= / TO-DATE= /

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVF002 S U B M I T - N E T dd.mm.yy/hh:mm:ss NET-NAME= NET-TEXT=

NET-STATUS =

PLAN-START = / LATEST-START = LIFE-TIME =

EARLIEST-START = /

RUN-CONTROL-SYSTEM= OPERATOR-START=

NET-DELAY-SOLUTION=

NET-TYPE =

CMD: OPR:

MSG:

U5184-J-Z125-7-76 323

System masks AVF004/012



AVAS-Vnn.yxmm/AVF004 S U B M I T - N E T dd.mm.yy/hh:mm:ss NET-NAME = NET-STATUS= NET-TEXT=


CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVF012 R E P E A T - N E T dd.mm.yy/hh:mm:ss NET-NAME= NET-TEXT=

NET-STATUS =

PLAN-START = / NEW-PLAN-START = /

LATEST-START = LIFE-TIME =

EARLIEST-START = /

RUN-CONTROL-SYSTEM= OPERATOR-START=

NET-DELAY-SOLUTION=

NET-TYPE =

CMD: OPR:

MSG:

324 U5184-J-Z125-7-76

AVF014 System masks


AVAS-Vnn.yxmm/AVF014 R E P E A T - N E T dd.mm.yy/hh:mm:ss NET-NAME = NET-STATUS= NET-TEXT=


NEW-PLAN-START= / EARLIEST-START= /

CMD: OPR:

MSG:

U5184-J-Z125-7-76 325

System masks AVI001/002

The parameter fields for mask AVI001 are described in "AVAS Job Handling" [2].


AVAS-Vnn.yxmm/AVI001 SHOW-PLAN-NET / NET-STRUCTURE dd.mm.yy/hh:mm:ss NET-NAME= NET-STATUS= NET-TEXT=

EARLIEST-START= / RUN-CONTROL-SYSTEM=

M IND FU TYPE NAME STATUS SYN- RESTART-IND IND V1 V2 V3

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVI002 S H O W - N E T - S T A T U S dd.mm.yy/hh:mm:ss NET-PARAMETER NET-NAME= NET-STATUS= NET-TEXT=

EARLIEST-START= / SUBMIT-TIME = / LATEST-START = / NET-START = / NET-DELAY-SOLUTION = STARTED-INDEX=

RUN-CONTROL-SYSTEM =

NET-TYPE = NET-CAT = NET-USER = NET-ACCOUNT = NET-CLASS = NET-LOG =

NET-PARAMETER=

CMD: OPR:

MSG:

326 U5184-J-Z125-7-76

AVI003/004 System masks



AVAS-Vnn.yxmm/AVI003 S H O W - N E T - S T A T U S dd.mm.yy/hh:mm:ss JOB-PARAMETER NET-NAME = NET-STATUS= JOB-NAME = JOB-STATUS= JOB-INDEX = FU= JOB-TYPE = SYNC-INDEX = RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3 LATEST-START = / DELAY-SOLUTION= MONJV( , )= VALUE( , )= ENTER-PARAMS = JOB-CAT = USER = JOB-ACCOUNT = JOB-CLASS = LOG = JOB-PARAMETER=

ENTER-FILE =

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVI004 S H O W - N E T - S T A T U S dd.mm.yy/hh:mm:ss CONDITION-PARAMETER NET-NAME = NET-STATUS=




COND-JVA-NAME= JVA-POSITION = JVA-LENGTH= COND-VALUE =

CMD: OPR:

MSG:

U5184-J-Z125-7-76 327


The parameter fields for mask AVI005 are described in “AVAS Job Handling“ [2].


AVAS-Vnn.yxmm/AVI005 S H O W - J O U R N A L dd.mm.yy/hh:mm:ss NET-NAME = NET-STATUS= /

M COMMAND ACT/RES DATE TIME IND F NAME / / / / / / / / / / / / / / SEL-NAME = SEL-INDEX= FROM-DATE = /

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVI006 S H O W - J O U R N A L dd.mm.yy/hh:mm:ss

NET-NAME = NET-STATUS= /

COMMAND =ACTION/RESULT=DATE/TIME = /AVAS-USER =INDEX =FUNCTION =NAME =OUTPUT-KEY = -OUTPUT-AREA :

CMD: OPR:

MSG:

328 U5184-J-Z125-7-76








CONDITION CREATED BY: NET-NAME= INDEX= OCCURE-VALUE =

ERROR-VALUE =


MSG:




COND-VALUE =

CMD: OPR:

MSG:

U5184-J-Z125-7-76 329








CMD: OPR:

MSG:




DATE = TIME =

CMD: OPR:

MSG:

330 U5184-J-Z125-7-76




AVAS-Vnn.yxmm/AVI011 S H O W - P L A N - N E T dd.mm.yy/hh:mm:ss

M NET-NAME EARLIEST-START IND NET-STATUS

/ / / / / / / / / / / / / / / FROM-DATE = / TO-DATE= /

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVI012 S H O W - N E T - S T A T U S dd.mm.yy/hh:mm:ss LIST-OF-NETSM NET-NAME EARLIEST-START IND NET-STATUS/CALLED FOR OBJ / / / / / / / / / / / / / / / FROM-DATE = / TO-DATE= /

CMD: OPR:

MSG:

U5184-J-Z125-7-76 331




AVAS-Vnn.yxmm/AVI013 S H O W - N E T - S T A T U S dd.mm.yy/hh:mm:ss NET-STRUCTURE

NET-NAME = NET-STATUS=

M IND FU TYPE NAME STATUS SYN- RESTART-IND IND V1 V2 V3

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVI014 S H O W - J O U R N A L dd.mm.yy/hh:mm:ss LIST OF NETS M NET-NAME PLAN-START NET-STATUS

/ / / / / / / / / / / / / / / / / / / / / / / / / / / / / / FROM-DATE = / TO-DATE = /

CMD: OPR:

MSG:

332 U5184-J-Z125-7-76


The parameter fields for mask AVI015 are described on page 64 onwards.


AVAS-Vnn.yxmm/AVI015 S H O W - F O R M A T dd.mm.yy/hh:mm:ss FORMAT LIST M FORMAT-NAME DATE

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVI016 SHOW/DELETE/ADD-JOBLOG dd.mm.yy/hh:mm:ss

M NET-NAME RESULT

CMD: OPR:

MSG:

U5184-J-Z125-7-76 333




AVAS-Vnn.yxmm/AVI017 SHOW/DELETE/ADD-JOBLOG dd.mm.yy/hh:mm:ss

NET-NAME=

M DATE CATID TSN IND JOB-NAME STATUS RESULT

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVI018 SHOW/ADD-JOBLOG dd.mm.yy/hh:mm:ss

NET-NAME= DATE = CATID= TSN=

INDEX = JOB-NAME=

M JOBLOG-NAME STATUS RESULT

CMD: OPR:

MSG:

334 U5184-J-Z125-7-76

AVI020 System masks


AVAS-Vnn.yxmm/AVI020 S H O W - N E T - S T A T U S dd.mm.yy/hh:mm:ss SERVER-JOB-PARAMETER NET-NAME = NET-STATUS= JOB-NAME = JOB-STATUS= JOB-INDEX = FU= JOB-TYPE = SYNC-INDEX = RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3 LATEST-START = / DELAY-SOLUTION= MONJV( , )= VALUE( , )= ENTER-PARAMS = JOB-CAT = USER = JOB-ACCOUNT = JOB-CLASS = LOG = JOB-PARAMETER=

SERVER-NAME= FILENAME =CMD: OPR:

MSG:

U5184-J-Z125-7-76 335

System masks AVM001/010

The parameter fields for mask AVM001 are described in "AVAS Job Handling" [2].


AVAS-Vnn.yxmm/AVM001 CREATE- / MODIFY - P R O D - N E T dd.mm.yy/hh:mm:ss NET-NAME= NET-STATUS= NET-TEXT=

M IND FU TYPE NAME STATUS SYN-IND RESULT

USER-PAR-FILE=CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVM010 C O L L E C T - N E T - P A R A M S dd.mm.yy/hh:mm:ss

M NET-NAME NET-STATUS RESULT

CMD: OPR:

MSG:

336 U5184-J-Z125-7-76

AVM011/012 System masks



AVAS-Vnn.yxmm/AVM011 C O L L E C T - N E T - P A R A M S dd.mm.yy/hh:mm:ss NET-NAME = NET-TEXT =

M FORMAT-NAME FORMAT-TEXT RESULT

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVM012 C R E A T E - P R O D - N E T dd.mm.yy/hh:mm:ss

M NET-NAME EARLIEST-START IND NET-STATUS RESULT USER-PAR-FILE /

/

/

/

/

/

/

/

USER-PAR-FILE (*NONE)=CMD: OPR:

MSG:

U5184-J-Z125-7-76 337

System masks AVM013/020



AVAS-Vnn.yxmm/AVM013 CREATE-PROD-JOB dd.mm.yy/hh:mm:ss

M FU INPUT-NAME DATE OUTPUT-NAME OVERWRITE RESULT

USER-PAR-FILE=CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVM020 P R O D - N E T - H A N D L I N G dd.mm.yy/hh:mm:ss

M NET-NAME NET-STATUS RESULT

CMD: OPR:

MSG:

338 U5184-J-Z125-7-76

AVN001/002 System masks

The parameter fields for mask AVN001 are described on page 133 onwards.


AVAS-Vnn.yxmm/AVN001 N E T - P A R A M S dd.mm.yy/hh:mm:ss

NET-NAME= NET-TEXT=

NET-DOC =

NET-TYPE =

RUN-CONTROL-SYSTEM=

USER-PAR-FILE=

NET-CAT =

NET-USER = NET-ACCOUNT = NET-PASSWORD= NET-CLASS = NET-LOG = NET-PARAMETER=

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVN002 JOB-DESCRIPTION FOR NET-STRUCTURE dd.mm.yy/hh:mm:ss

JOB-NAME = NET-NAME= JOB-TEXT =

JOB-DOC = JOB-INDEX = FU= JOB-TYPE= SYNC-INDEX = RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3 ENTER-PARAMS = JOB-CAT = USER = JOB-ACCOUNT = PASSWORD= JOB-CLASS = LOG = JOB-PARAMETER=

ENTER-FILE = FILE-PASSWORD=

CMD: OPR:

MSG:

U5184-J-Z125-7-76 339

System masks AVN003/004



AVAS-Vnn.yxmm/AVN003 CONDITION-DESCR. FOR NET-STRUCTURE dd.mm.yy/hh:mm:ss

COND-NAME = NET-NAME= COND-TEXT =

COND-DOC = COND-INDEX = FU= COND-TYPE= SYNC-INDEX = RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3

COND-JVA-NAME= JVA-POSITION = JVA-LENGTH= JVA-PASSWORD= COND-VALUE =

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVN004 N E T - S T R U C T U R E dd.mm.yy/hh:mm:ss

NET-NAME= NET-TEXT=

M IND FU TYPE NAME SYNC- RESTART-IND RESULT INDEX V1 V2 V3

NEXT=CMD: OPR:

MSG:

340 U5184-J-Z125-7-76




AVAS-Vnn.yxmm/AVN005 N E T - S T R U C T U R E dd.mm.yy/hh:mm:ss NET-NAME= NET-TEXT=

M IND FU TYPE NAME SYN- RESTART-IND RESULT IND V1 V2 V3

FROM-INDEX = TO-INDEX = AFTER-INDEX= COPY-NET-NAME= OVERWRITE=

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVN006 N E T - F O R M A T S dd.mm.yy/hh:mm:ss NET-NAME= NET-TEXT=

M FORMAT-NAME FORMAT-TEXT

CMD: OPR:

MSG:

U5184-J-Z125-7-76 341




AVAS-Vnn.yxmm/AVN007 CHANGE-NET-DESCRIPTION dd.mm.yy/hh:mm:ss

OLD-USER = OLD-ACCOUNT= OLD-PASSWORD= NEW-USER = NEW-ACCOUNT= NEW-PASSWORD= (RETENTION-PERIOD= OF CHANGE-NET-DESCRIPTION USER/ACCOUNT/PASSWORD)

OLD-CLASS= OLD-LOG = NEW-CLASS= NEW-LOG =

OLD-CAT = NEW-CAT =

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVN08 CONDITION-DESCR. FOR NET-STRUCTURE dd.mm.yy/hh:mm:ss COND-NAME = NET-NAME= COND-TEXT =



OCCURE-VALUE =

ERROR-VALUE =

SELECT-RESTART-VARIANT=

CMD: OPR:

MSG:

342 U5184-J-Z125-7-76




AVAS-Vnn.yxmm/AVN009 SERVER-JOB-DESCRIPTION FOR NET-STRUC. dd.mm.yy/hh:mm:ss


JOB-DOC = JOB-INDEX = FU= JOB-TYPE= SYNC-INDEX = RESTART -INDEX -NAME -TYPE AUTOMATIC VARIANT=1 2 3 ENTER-PARAMS = JOB-CAT = USER = JOB-ACCOUNT= PASSWORD= JOB-CLASS = LOG = JOB-PARAMETER=

SERVER-NAME= SERVER-PASSWORD= FILENAME =

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVN011 N E T - H A N D L I N G dd.mm.yy/hh:mm:ss

M NET-NAME DATE IND RESULT OBJ

CMD: OPR:

MSG:

U5184-J-Z125-7-76 343




AVAS-Vnn.yxmm/AVN012 COPY-NET-DESCRIPTION dd.mm.yy/hh:mm:ss

M NET-NAME DATE IND COPY-NET-NAME OVER- RESULT WRITE

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVN020 N E T - P A R A M S dd.mm.yy/hh:mm:ss

NET-NAME= NET-TEXT=

SELECT-TURNUS= M PLAN-START LATEST- DELAY- LIFE-TIME SYMDAT / DATE TIME START SOLUTION

CMD: OPR:

MSG:

344 U5184-J-Z125-7-76




AVAS-Vnn.yxmm/AVN021 JOB-DESCRIPTION FOR NET-STRUCTURE dd.mm.yy/hh:mm:ss


JOB-INDEX = FU= JOB-TYPE= SELECT-TURNUS=

M SYMDAT LATEST- DELAY- LIFE-TIME START SOLUTION

CMD: OPR:

MSG:



COND-INDEX = FU= COND-TYPE= SELECT-TURNUS=

M SYMDAT LATEST- DELAY- OCCURE SOLUTION

CMD: OPR:

MSG:

U5184-J-Z125-7-76 345







M OCCURE-DATE OCCURE- SYMDAT TIME

CMD: OPR:

MSG:




M SYMDAT

CMD: OPR:

MSG:

346 U5184-J-Z125-7-76







COND-VALUE =

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVN031 CONDITION-DESCR. FOR NET-STRUCTURE dd.mm.yy/hh:mm:ss COND-NAME = NET-NAME= COND-TEXT =



CMD: OPR:

MSG:

U5184-J-Z125-7-76 347

System masks AVN032





CMD: OPR:

MSG:

348 U5184-J-Z125-7-76

AVP001/003 System masks

The parameter fields for mask AVP001 are described in "AVAS Job Handling" [2].


AVAS-Vnn.yxmm/AVP001 C R E A T E - P L A N - N E T dd.mm.yy/hh:mm:ss NET-NAME = NET-TEXT=

M IND FU TYPE NAME SYN- RESTART-IND RESULT IND V1 V2 V3

EARLIEST-START= / LATEST-START= LIFE-TIME=SYMDAT-NAME = RUN-CONT-SYS= SELECT-TURNUS=

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVP003 P L A N - N E T - H A N D L I N G dd.mm.yy/hh:mm:ss

NET-NAME = NET-TEXT=

NET-STATUS =

PLAN-START = /

EARLIEST-START = / LATEST-START = NET-DELAY-SOLUTION=

LIFE-TIME =

RUN-CONTROL-SYSTEM=

NET-TYPE =

CMD: OPR:

MSG:

U5184-J-Z125-7-76 349

System masks AVP010/011



AVAS-Vnn.yxmm/AVP010 P L A N - N E T - H A N D L I N G dd.mm.yy/hh:mm:ss

M NET-NAME EARLIEST-START NET-STATUS RESULT

/ / / / / / / / / / / / / / / FROM-DATE= / TO-DATE= /

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVP011 C R E A T E - P L A N - N E T dd.mm.yy/hh:mm:ss

M NET-NAME EARLIEST-START RUN-CONT SEL- RESULT -SYSTEM TUR / / / / / / / / / / / / / / ALTERN-RUN-CONT-SYS= FROM-DATE = / TO-DATE= /

CMD: OPR:

MSG:

350 U5184-J-Z125-7-76

AVS010/011 System masks

The parameter fields for mask AVS010 are described on page 11 onwards.


AVAS-Vnn.yxmm/AVS010 A V A S - S I G N O N dd.mm.yy/hh:mm:ss

PLEASE ENTER IDENTIFICATION

AVAS-USER-ID : PASSWORD : AVAS-SYSTEM-ID :

NEW-PASSWORD : REPEAT-NEW-PASSWORD :

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVS011 C O P Y - E L E M E N T dd.mm.yy/hh:mm:ss AVAS-USER-LIBRARY= MODE= OVERWRITE= EXTERNAL-FILE = ELEMENT/GROUP = M ELEMENT-NAME DATE RESULT

CMD: OPR:

MSG:

U5184-J-Z125-7-76 351

System masks AVS015/016

The parameter fields for mask AVS015 are described on page 24.


AVAS-Vnn.yxmm/AVS015 A V A S - P R I N T - P A R A M S dd.mm.yy/hh:mm:ss

LIST-FILE-NAME=

EXTEND=

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVS016 E D I T - D O C U M E N T dd.mm.yy/hh:mm:ss

DOCUMENT-NAME=

NEW-DOCUMENT-NAME=

OVERWRITE=

CMD: OPR:

MSG:

352 U5184-J-Z125-7-76

AVS019/020 System masks


In mask AVS020 only those functions are displayed which the calling user is authorizedto use.

AVAS-Vnn.yxmm/AVS019 D O C U M E N T - H A N D L I N G dd.mm.yy/hh:mm:ss

M DOCUMENT-NAME DATE RESULT

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVS020 AVAS-COMMAND-SUMMARY dd.mm.yy/hh:mm:ss ==================== M

CMD: OPR:

MSG:

U5184-J-Z125-7-76 353

System masks AVS025/030

In mask AVS025 the HELP texts requested by the user via CMD:? are displayed.

Mask AVS030 (an empty mask) is displayed when there is no active statement or whencontrol is to be switched from one statement to another.

AVAS-Vnn.yxmm/AVS025 HELP FOR COMMAND dd.mm.yy/hh:mm:ss

CMD: OPR:

MSG:

AVAS-Vnn.yxmm/AVS030 A V A S - S Y S T E M dd.mm.yy/hh:mm:ss =======================

CMD: OPR:

MSG:


U5184-J-Z125-7-76 355

9 Listings for job managementWith some interactive functions it is possible to have listings or logs of the displayed oredited data output to the file specified under LIST-FILE-NAME via a SAM interface.

All listings are output in a printable format. The record length must not exceed 132 printpositions.

This operation is initiated by means of the PRINT operation. Following CMD:PRINT, AVASdisplays the AVS015 mask containing the name of the SAM file for the list output. When theprint function is called for the first time, the default name is output in the LIST-FILE-NAMEparameter field in the form LST.AVAS.ug.avuser.yyyymmdd.hhmmss (see print function,page 24).

LST.AVAS.ug.avuser.yyyymmdd.hhmmss

where:

ug Name of the user group.

avuser Name of the user (up to eight characters long).

yyyymmdd.hhmmss Date and time of the output file.

If the specified file already exists, the data to be output will be added to it.

356 U5184-J-Z125-7-76

SHOW-NET-DESCRIPTION listing Listings for job management

9.1 SHOW-NET-DESCRIPTION listing

The following listings can be created using the SHOW-NET-DESCRIPTION statement withCMD:PRINT:

AVL001: Net parameters and net plan data

AVL002: Listing of net masks

AVL003: Net structure, list of the structure elements

AVL004: Parameters and plan data of a structure element (FU=J/P/X)

AVL005: Parameters and plan data of a condition/time structure element

AVL006: List of nets--------------------------------------------------------------Mask CMD:PRINT Listing -------------->--------------------------------------------------------------AVN011 ---> AVL001 AVL002 AVL003 AVL006

AVN001 ---> AVL001AVN020 ---> AVL001

AVN006 ---> AVL002

AVN004 ---> AVL003

AVN002 ---> AVL004AVN009 ---> AVL004AVN021 ---> AVL004

AVN003 ---> AVL005AVN008 ---> AVL005AVN030 ---> AVL005AVN030 ---> AVL005AVN031 ---> AVL005AVN032 ---> AVL005AVN022 ---> AVL005AVN023 ---> AVL005AVN024 ---> AVL005

U5184-J-Z125-7-76 357

SHOW-NET-DESCRIPTION listing AVL001/AVl002 listings

AVL001 listing: SHOW-NET-DESCRIPTION / NET-PARAMETER

1 10 20 30 40 50 60 70 80 90 100 110 120 130+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-AVAS-Vnn.yxmm/AVL001 CMD:SHOW-NET-DESCRIPTION OBJECT:NET-PARAMETER AVAS-USER:avuser DATE:dd.mm.yy TIME:hh:mm:ss PAGE:nnn

NET-NAME=

NET-TEXT=

NET-DOC =RUN-CONTROL-SYSTEM=NET-TYPE =SELECT-TURNUS =USER-PAR-FILE =NET-CAT =NET-USER =NET-ACCOUNT =NET-CLASS =NET-LOG =NET-PARAMETER =SELECT-TURNUS =

PLAN-START LATEST-START DELAY-SOLUTION LIFE-TIMEDATE / SYMDAT TIME*NONE . . . . . . . . . . . . . .+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-1 10 20 30 40 50 60 70 80 90 100 110 120 130

AVL002 listing: SHOW-NET-DESCRIPTION / NET-FORMAT

1 10 20 30 40 50 60 70 80 90 100 110 120 130+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-AVAS-Vnn.yxmm/AVL002 CMD:SHOW-NET-DESCRIPTION OBJECT:NET-FORMAT AVAS-USER:avuser DATE:dd.mm.yy TIME:hh:mm:ss PAGE:nnn

NET-NAME=

NET-TEXT=

FORMAT-NAME FORMAT-TEXT

. . . . . .+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-1 10 20 30 40 50 60 70 80 90 100 110 120 130

358 U5184-J-Z125-7-76

AVL003 listing SHOW-NET-DESCRIPTION listing

AVL003 listing: SHOW-NET-DESCRIPTION / NET-STRUCTURE

1 10 20 30 40 50 60 70 80 90 100 110 120 130+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-AVAS-Vnn.yxmm/AVL003 CMD:SHOW-NET-DESCRIPTION OBJECT:NET-STRUCTURE AVAS-USER:avuser DATE:dd.mm.yy TIME:hh:mm:ss PAGE:nnn

NET-NAME=

NET-TEXT=

INDEX FU TYPE NAME SYNC.- RESTART-INDEX INDEX V1 V2 V3

. . . . . . . . . . . . . . . . . . . . . . . .+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-1 10 20 30 40 50 60 70 80 90 100 110 120 130

U5184-J-Z125-7-76 359

SHOW-NET-DESCRIPTION listing AVL004 listing

AVL004 listing: SHOW-NET-DESCRIPTION / JOB-PARAMETER

1 10 20 30 40 50 60 70 80 90 100 110 120 130+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-AVAS-Vnn.yxmm/AVL004 CMD:SHOW-NET-DESCRIPTION OBJECT:JOB-PARAMETER AVAS-USER:avuser DATE:dd.mm.yy TIME:hh:mm:ss PAGE:nnn

NET-NAME=

NET-TEXT=

JOB-NAME=JOB-TEXT=

JOB-DOC =FUNCTION =JOB-TYPE =JOB-INDEX =

SYNC-INDEX=

RESTART-VARIANT -INDEX -JOB/COND-NAME -TYPE AUTOMATIC 1 2 3ENTER-PARAMS =JOB-CAT =USER =JOB-ACCOUNT =JOB-CLASS =LOG =JOB-PARAMETER= -------------ENTER-FILE = |FILENAME = | -> Only the parameters which are possibleSERVER-NAME= | for the function FU will be output.USER-PAR-FILE= | -------------

SELECT-TURNUS=

SYMDAT-NAME LATEST-START DELAY-SOLUTION LATEST-START . . . . . . . . . . . .+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-1 10 20 30 40 50 60 70 80 90 100 110 120 130

360 U5184-J-Z125-7-76

AVL005 listing SHOW-NET-DESCRIPTION listing

AVL005 listing: SHOW-NET-DESCRIPTION / CONDITION-PARAMETER

1 10 20 30 40 50 60 70 80 90 100 110 120 130+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-AVAS-Vnn.yxmm/AVL005 CMD:SHOW-NET-DESCRIPTION OBJECT:CONDITION-PARAMETER AVAS-USER:avuser DATE:dd.mm.yy TIME:hh:mm:ss PAGE:nnn

NET-NAME=

NET-TEXT=

COND-NAME =COND-TEXT =

COND-DOC =FUNCTION =COND-TYPE =COND-INDEX=

SYNC-INDEX=RESTART-VARIANT -INDEX -JOB/COND-NAME -TYPE AUTOMATIC

1 2 3 ----------------------COND-JVA-NAME= |JVA-POSITION = |JVA-LENGTH = |COND-VALUE = |CONDITION CREATED BY: |NET-NAME = --> Only the parameters which are

INDEX = | possible for the function FUOCCURE-VALUE = | and TYPE will be output. |ERROR-VALUE = | |SELECT-RESTART-VARIANT= | ----------------------SELECT-TURNUS=SYMDAT LATEST-OCCURE DELAY-SOLUTIONOCCURE-DATE OCCURE-TIME . . . . . . . . . . . .+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-1 10 20 30 40 50 60 70 80 90 100 110 120 130

U5184-J-Z125-7-76 361

SHOW-NET-DESCRIPTION listing AVL006 listing

AVL006 listing: SHOW-NET-DESCRIPTION/NET-LIST

1 10 20 30 40 50 60 70 80 90 100 110 120 130+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-AVAS-Vnn.yxmm/AVL006 CMD:SHOW-NET-DESCRIPTION OBJECT:NET-LIST AVAS-USER:avuser DATE:dd.mm.yy TIME:hh:mm:ss PAGE:nnn

NET-NAME PLAM-DATE

. . . . . . . . . .

+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-1 10 20 30 40 50 60 70 80 90 100 110 120 130

362 U5184-J-Z125-7-76

AVL035 listing SHOW-DOCUMENT listing

9.2 SHOW-DOCUMENT listing

The following listing can be created using the SHOW-DOCUMENT statement withCMD:PRINT:

AVL035: Data records of the documentation element

--------------------------------------------------------------Mask CMD:PRINT Listing -------------->--------------------------------------------------------------AVS019 ---> AVL035

AVL035 listing: SHOW-DOCUMENT / DOCUMENT-LIST

1 10 20 30 40 50 60 70 80 90 100 110 120 130+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-AVAS-Vnn.yxmm/AVL035 CMD:SHOW-DOCUMENT OBJECT:DOCUMENT-LIST AVAS-USER:avuser DATE:dd.mm.yy TIME:hh:mm:ss PAGE:nnn

DOCUMENT-NAME=

. . . . .+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-1 10 20 30 40 50 60 70 80 90 100 110 120 130

U5184-J-Z125-7-76 363

SHOW-JOB listing AVL041 listing

9.3 SHOW-JOB listing

The following listings can be created using the SHOW-JOB statement with CMD:PRINT

AVL041: Data records of the job

--------------------------------------------------------------Mask CMD:PRINT Listing -------------->--------------------------------------------------------------AVE010 ---> AVL041

AVL041 listing: SHOW-JOB / JOB-LIST

1 10 20 30 40 50 60 70 80 90 100 110 120 130+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-AVAS-Vnn.yxmm/AVL041 CMD:SHOW-JOB OBJECT:JOB-LIST AVAS-USER:avuser DATE:dd.mm.yy TIME:hh:mm:ss PAGE:nnn

JOB-NAME= FUNCTION

+---+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+-1 10 20 30 40 50 60 70 80 90 100 110 120 130


U5184-J-Z125-7-76 365

List of statements

Statement Function Page

ADD-COND-DESCRIPTION Create a condition description 213

CANCEL-NET Interrupt or abort a net due to an error [2]

CHANGE-NET-DESCRIPTION Large-scale changes to nets 191

COLLECT-NET-PARAMS Collect parameters for modifying all tasks in a net [2]

COPY-CALENDAR Copy a calendar with its SYMDATs 256

COPY-ELEMENT Copy library elements from/to an external file or library 207

COPY-NET-DESCRIPTION Copy a net description 196

CREATE-CALENDAR Set up a new calendar 238

CREATE-NET-DESCRIPTION Create a net description 130

CREATE-PERIOD Create a period [2]

CREATE-PLAN-NET Plan the processing of a net [2]

CREATE-PROD-JOB Create static jobs, server jobs and S procedures [2]

CREATE-PROD-NET Create temporary jobs, server jobs and S proceduresof net

[2]

DELETE-CALENDAR Delete a calendar 258

DELETE-COND-DESCRIPTION Delete a condition description 228

DELETE-DOCUMENT Delete documentation elements 110

DELETE-JOB Delete jobs, S procedures, server jobs and JCLelements

102

DELETE-NET-DESCRIPTION Delete a net description 205

DELETE-PERIOD Delete a period [2]

DELETE-PLAN-NET Delete planned nets from a production plan [2]

DELETE-PROD-JOB Delete static tasks [2]

DELETE-PROD-NET Delete all temporary tasks of a net [2]

EDIT-DOCUMENT Edit documentation elements 106

EDIT-JOB Edit jobs, S procedures, server jobs and JCL elements 95

EDIT-PROD-JOB Edit executable jobs, server jobs and S procedures [2]

EDT Edit external SAM/ISAM user files 104

366 U5184-J-Z125-7-76

List of statements

HOLD-NET Suspend nets which are currently being executed [2]

MODIFY-CALENDAR Modify a calendar 244

MODIFY-COND-DESCRIPTION Modify a condition description 217

MODIFY-NET-DESCRIPTION Modify a net description 186

MODIFY-PERIOD Modify a period [2]

MODIFY-PLAN-NET Modify planned nets in the production plan [2]

MODIFY-PROD-NET Delete individual tasks of a net [2]

MODIFY-SUBMIT-JOB Modify tasks of a released net [2]

MODIFY-SUBMIT-NET Modify a released net [2]

REPEAT-NET Repeat release of a planned net [2]

RESTART-NET Restart an abnormally terminated net [2]

RESUME-NET Cancel the HOLD state [2]

SHOW-CALENDAR Display a calendar 254

SHOW-COND-DESCRIPTION Display a condition description 231

SHOW-DOCUMENT Display documentation elements 108

SHOW-FORMAT Display a user mask 63

SHOW-JOB Display jobs, S procedures, server jobs and JCLelements

100

SHOW-JOB-LOG Display logs [2]

SHOW-JOURNAL Display journal records [2]

SHOW-NET-DESCRIPTION Display a net description 200

SHOW-NET-STATUS Display the status of released or running nets [2]

SHOW-PERIOD Display a period [2]

SHOW-PLAN-NET Display the processing status of planned nets [2]

SHOW-PROD-JOB Display executable tasks [2]

START-NET Start processing of net regardless of start conditions [2]

SUBMIT-NET Release planned nets [2]

Statement Function Page

U5184-J-Z125-7-76 367

List of masks

AVC... Masks for calendar and period functions Page(s)

AVC001 Set up a calendar 239, 307

AVC002 Display a calendar for modification 246, 246, 307

AVC010 Overview of a calendars 253, 308

AVC012 Copy calendars 257, 309

AVC020 Set up/modify a period [2], 309

AVC021 Overview of periods [2], 310

AVD... Masks for run control functions Page(s)

AVD001 Display net parameters for modification [2], 311

AVD002 Display parameters of a control record with FU=J/P for modification [2], 311

AVD003 Display parameters of a structure element with FU=C andTYPE=JVA for modification

[2], 312

AVD004 Overview of structure elements of net [2], 312

AVD005 Display the structure elements of the restart point [2], 313

AVD006 Display the parameters of a task with FU=J/P/X after modifying theJCL

[2], 313

AVD007 Display the structure elements of a net for selection of the point-of-error

[2], 314

AVD008 Overview of the structure elements in a net [2], 314

AVD009 Display the parameters of a structure element with FU=C andTYPE=NET/JOB/RES/VAL for modification

[2], 315

AVD010 Display the parameters of a structure element with FU=A/M/D andTYPE=RES/VAL for modification

[2], 315

AVD011 Overview of nets in a run control system [2], 316

AVD012 Overview of nets with ERROR status [2], 316

AVD015 Overview of the nets in a processing system [2], 317

AVD016 Display the parameters of a structure element with FU=D andTYPE=NET/JOB for modification

[2], 317

AVD017 Display the parameters of a structure element with FU=W andTYPE=TIM for modification

[2], 318

368 U5184-J-Z125-7-76

List of masks

AVD018 Display the parameters of a structure element with FU=X for modifi-cation

[2], 318

AVD030 Display the parameters of a condition description 215, 233, 319

AVD031 Display the users of a condition description 224, 319

AVD040 Overview of the condition descriptions 220, 320

AVE... Masks for editing jobs, S procedures, server jobs and JCLelements

Page(s)

AVE010 Overview of jobs, S procedures, server jobs and JCL elements 97, 321

AVE011 Display after terminating EDT 98, 321

AVF... Masks for releasing runs Page(s)

AVF001 Overview of a net group for release [2], 322

AVF002 Net information for net release [2], 322

AVF004 Overview of the structure elements of a net [2], 323

AVF012 Display net parameters [2], 323

AVF014 Overview of the structure elements of a net [2], 324

AVI... Masks for current information Page(s)

AVI001 Information on processing status of net - overview of structureelements

[2], 325

AVI002 Processing status of net - net parameters + status [2], 325

AVI003 Processing status of a task with FU=J/P - job parameters + status [2], 326

AVI004 Processing status of a structure element with FU=C andTYPE=JVA - parameters + status

[2], 326

AVI005 Display the key area of selected journal records of a net [2], 327

AVI006 Display journal records of a net with data area [2], 327

AVI007 Processing status of a structure element with FU=C andTYPE=NET/JOB/RES/VAL - parameters + status

[2], 328

AVI008 Processing status of a structure element with FU=A/M/D andTYPE=RES/VAL - parameters + status

[2], 328

AVI009 Processing status of a structure element with FU=D andTYPE=NET/JOB - parameters + status

[2], 329

AVI010 Processing status of a structure element with FU=W and TYPE=TIM- parameters + status

[2], 329

AVI011 Overview of nets with processing status (NPRLIB) [2], 330

AVI012 Overview of nets with processing status (ABLDAT) [2], 330

AVD... Masks for run control functions Page(s)

U5184-J-Z125-7-76 369

List of masks

AVI013 Processing status of net - overview of structure elements [2], 331

AVI014 Overview of nets in the journal file [2], 331

AVI015 Overview of user masks 64, 332

AVI016 Overview of nets in the log file [2], 332

AVI017 Overview of job runs [2], 333

AVI018 Overview of log entries for a job run [2], 333

AVI020 Processing status of a structure element with FU=X- parameters + status

[2], 334

AVM... Masks for modification Page(s)

AVM001 Overview of tasks of a net for modification [2], 335

AVM010 Overview of nets for collecting netwide parameters [2], 335

AVM011 Overview of the masks assigned to a net [2], 336

AVM012 Overview of nets selected for modification [2], 336

AVM013 Overview of jobs, S procedures, SINIX jobs in JCLLIB or JCLSYS [2], 337

AVM020 Overview of nets in NPRLIB [2], 337

AVN... Masks for net editing Page(s)

AVN001 Parameters for net control records 133, 338

AVN002 Parameters for structure elements with FU=J/P 151, 338

AVN003 Parameters for structure elements with FU=C and TYPE=JVA 157, 339

AVN004 Overview of the structure elements in a net 143, 189, 339

AVN005 Display a net description for copying 199, 340

AVN006 Parameters for defining the net masks 142, 340

AVN007 Net description parameters for modification 193, 341

AVN008 Parameters for structure elements with FU=C and TYPE=NET/JOB/RES/VAL

162, 341

AVN009 Parameters for structure elements with FU=X 167, 342

AVN011 Overview of net descriptions 187, 192, 342

AVN012 Overview of net descriptions for copying 198, 343

AVN020 Plan data for a net 138, 343

AVN021 Plan data for a structure element with FU=J/P/X 176, 344

AVN022 Plan data for a structure element with FU=C 180, 344

AVN023 Plan data for a structure element with FU=W 183, 345

AVI... Masks for current information Page(s)

370 U5184-J-Z125-7-76

List of masks

AVN024 Plan data for a structure element with FU=A/M/D and TYPE=RES/VAL or with FU=D and TYPE=NET/JOB

185, 345

AVN030 Parameters of structure elements with FU=A/M/D and TYPE=RES/VAL

173, 346

AVN031 Parameters of structure elements with FU=D and TYPE=NET/JOB 175, 346

AVN032 Parameters of structure elements with FU=W and TYPE=TIM 175, 347

AVP... Masks for production planning Page(s)

AVP001 Plan net without a calendar [2], 348

AVP003 Display a planned net for modification [2], 348

AVP010 Overview of planned nets [2], 349

AVP011 Overview of nets selected from the net library for planning [2], 349

AVS... System dialog masks Page(s)

AVS010 AVAS signon mask 11, 350

AVS011 Input/output of AVAS library elements 210, 350

AVS015 Mask for entry of print parameters 24, 351

AVS016 Output after editing documentation elements 107, 351

AVS019 Overview of documentation files 107, 352

AVS020 Overview of AVAS functions 352

AVS025 Display help text for AVAS function 353

AVS030 Empty mask 353

AVN... Masks for net editing Page(s)

U5184-J-Z125-7-76 371

GlossaryABLDAT

Link name for the run control file.

ABLDUPLink name for the copy of the run control file.

automatic restartAVAS automatically restarts an errored net at the relevant restart point.

AVAS reportEvaluation of the AVAS production plan and the AVAS journal file according topredefined criteria.

AVAS-SYSTEM-LIBRARYName of a central AVAS library.

AVAS-USER-LIBRARYName of an AVAS user library.

batch statementsBatch statements are selected statements which can be entered in procedures.

calendarList of days, delimited by a start date and an end date. Each day is assigned aday of the week. Each day can also be assigned one or more symbolic startdates. Each user group is assigned a calendar. Calendars are stored andmanaged under unique names in the CALLIB.

CALLIBLink name for the calendar library.

conditionPrerequisite for starting a net or an index level of a net; see also CONDITION-TYPE.

372 U5184-J-Z125-7-76

Glossary

condition descriptionPart of the ABLDAT for conditions of type NET/JOB/RES/VAL; a record containsall the necessary information for the CONDITION-TYPE concerned.

CONDITION-JVA-NAMEName of the job variable which has to assume a desired value at a certainposition in order to satisfy the structure variable’s condition.

CONDITION-TEXTBrief description of the structure element.

CONDITION-TYPEThe type of a structure element which specifies a condition(NET/JOB/RES/VAL/JVA/TIM).

CONDITION-VALUEValue of a condition description of a job variable.

dependencySituation where a net or an index level of a net is waiting for an event to occurbefore the start can take place.

DELAY-SOLUTIONMeasures to be taken if a net is not started at the appropriate time.

DOCLIBLink name for the library containing the documentation elements.

DOCSYSLink name for the central library of documentation elements.

EARLIEST-STARTResolved start time provided for the net. It is formed with CREATE-PLAN-NETand can be modified by means of MOD-PLAN-NET and SUBM-NET. It is asearch criterion when nets are selected via the operand PERIOD-NAME, but itis not part of a name.

ENTER-FILEThis file is used to store the JCL of jobs not managed by AVAS(jobs with JOB-TYPE=EXT).

ENTER-PARAMSControl variable for supplying default values to the ENTER parameters of thejobs.

U5184-J-Z125-7-76 373

Glossary

EXTERNAL-FILEName of an external PLAM library or SAM file as an input or output file for trans-ferring AVAS library elements.

FILE-PASSWORDPassword for the ENTER-FILE.

FORMAT-NAMEName of a user mask.

FUNCTION (also FU or F)The function which a structure element performs within the net description. Thefunctions are:

J (Job) The specification required to execute a job

P (Procedure) The specification required to execute an S procedure

X (SV job) Description for the execution of a task on a server system

A (Add) Create a condition description

M (Modify) Amend a condition description

D (Delete) Delete a condition description

C (Compare) Test a condition descriptions

W (Wait) Wait until a date and time

index levelHierarchy level of the net structure. The structure elements of one index levelare processed or brought to execution simultaneously. The index levels areprocessed consecutively in ascending order if the index level was terminatednormally. If errors occur, processing is interrupted at the end of the index levelinvolved. The sequence in which an index level is processed (or waited for) canbe broken by specifying a synchronization index (SYNC-INDEX).

JCL elementExternally stored JCL of one or more jobs or S procedures. It is reincorporatedin the job or S procedure via an AVAS statement within the framework ofparameter modification.

JCLLIBLink name for the library of jobs, S procedures, SV jobs and JCL elements.

374 U5184-J-Z125-7-76

Glossary

JCLSYSLink name for the central library of jobs, S procedures, SV jobs and JCLelements.

JMDLIBLink name for the library of modified jobs, S procedures and SV jobs.

JMDSYSLink name for the central library of modified jobs, S procedures and SV jobs.

jobBS2000 command sequence beginning with ’/LOGON’ and ending with’/LOGOFF’. It is also possible to incorporate special AVAS statements in thecommand sequence.

JOB-ACCOUNTParameter for the ENTER call of the job, S procedure or server representative.

JOB-CLASSParameter for the ENTER call of the job, S procedure or server representative.

job control recordPart of the net description. It describes the position of the job or S procedurewithin the net as well as its parameters.

JOB-DOCName of the documentation element for a job, an S procedure or an SV job.

JOB-INDEXIndex level of a job, an S procedure or an SV job in the net.

JOB-LOGJob execution logs stored under AVAS.

JOBMAPLink name for the library of user masks related to individual jobs orS procedures.

JOB-PARAMETERParameter for the ENTER call of a job, an S procedure or a server represen-tative.

JOB-STATUSStatus indicator of a job, an S procedure or an SV job.

U5184-J-Z125-7-76 375

Glossary

JOB-TEXTBrief description of the job, S procedure or SV job.

JOB-TYPEIndicates how the JCL of a task (job, S procedure, SV job) is managed in theAVAS system and how the task is monitored via a job variable (STD / MOD /EXT / EXX).

journal fileOutput medium for logging the actions of the user on the AVAS system as wellas the run control system activities.

JRLDATLink name for the emergency journal file.

JRNDATLink name for the journal file.

JV-LENGTHLength of the value of a job variable.

JV-NAMEName of a job variable.

JV-PASSWORDPassword for a job variable.

JV-POSITIONStart position of the value in the job variable.

LATEST-STARTLatest start time for the net or a task in the net.

LIFE-TIMETime span relative to PLAN-START; indicates how long the event ’end of net’ or‘end of job’ is to remain valid and recognizable.

LOGParameter for the ENTER call of the job, S procedure or AVAS agentAVSSINCM.

LOGSYSLink name for the central job log library (AVAS pool).

376 U5184-J-Z125-7-76

Glossary

MColumn in the AVAS system masks where marks are entered to selectelements.

netSet of consecutive jobs, S procedures or SV jobs whose execution is structuredand defined in accordance with their logical and temporal interdependencies.

NET-ACCOUNTDefault value for JOB-ACCOUNT.

NET-CATCatalog identifier of a slave processor.

NET-CLASSDefault value for JOB-CLASS.

net control recordPart of the net description. It contains parameters valid throughout the net.

NET-DELAY-SOLUTIONAction for untimely net start.

net descriptionStructure description of the net and information on the contents and sequenceof processing steps within a net. It is created by production planning.

NET-DOCName of the documentation element for a net.

NETLIBLink name for the net description library.

NET-LOGDefault value for LOG.

NETMAPLink name for the library of user masks related to nets.

NET-NAMEName of the net.

NET-PARAMETERDefault value for JOB-PARAMETER.

U5184-J-Z125-7-76 377

Glossary

net processingProcessing of the net description (create, modify, copy, delete, display).

NET-STATUSStatus indicator for the net.

NETSYSLink name for the central net description library.

NET-TEXTBrief description of the net.

NET-TYPEControl variable for serializing the processing of two or more like-named nets(but with different start times).

NET-USERDefault value for USER.

NPRLIBLink name for the library of planned nets.

operationDialog control variable. It is entered via the CMD: field in the mask.

OUT-OF-PLAN reportThe OOP report lists nets which have exceeded a defined delay and/or whichhave a selected status.

PERDATLink name for the period file.

periodInterval delimited by start and end times. Periods are stored and managedunder unique names in a separate collection of data.

PLANNED-NET-MODIFICATION reportThe PNM report lists nets which have been modified after production planning.

planning periodTime span for which selected nets are scheduled to run. It is specified viaPERIOD-NAME. Those nets are processed whose symbolic start dates areentered in the calendar section corresponding to the planning period.

378 U5184-J-Z125-7-76

Glossary

PLAN-STARTStart time envisaged for the net. It is made part of the name of the nets in theNPRLIB during the planning operation and cannot be modified thereafter.

production plan"Directory" for the library of planned nets, i.e. a list of the planned nets withindividual resolved start times and production status.

release periodTime span during which two or more nets can be released together. It is set bythe PERIOD-NAME operand. Those nets are processed whose resolved starttimes lie in the release period.

REPORT generatorProcess for creating AVAS reports.

REPORT statementsInstructions to the REPORT generator.

resolved dependencyThe event on which the start of a net or an index level depends has occurred.The condition of a waiting net has been satisfied.

resolved start timeThis always consists of a date and a time of day and means that the symbolicstart date of a net has been replaced by a real date. This operation takes placeat the "production planning" stage.

RESTART-INDEXIndex level at which restart is to take place.

restart jobAdditional job that must be performed following an interrupt before normalprocessing can resume.

RESTART-NAMEName of the structure element at which any required restart is to take place.

RESTART-NETRestart of a previously interrupted net.

restart statementFacilities incorporated in the JCL for restart following an error.

U5184-J-Z125-7-76 379

Glossary

RESTART-TYPEThis indicates whether restart statements are to be processed in a restartsituation.

RESTART-VARIANTThis indicates which of the three possible restart variants is to be processed.Description of the three restart variants, consisting of RESTART-TYPE,RESTART-INDEX, RESTART-NAME.

run control fileFile containing all the information needed to control execution of linked runcontrol systems. At the "release for production" stage, the structure descriptionof the planned net and the corresponding JCL are added to the run control file.

run control system (RCS)This consists of an AVAS run control and monitoring routine with the namedefined at generation time (RUN-CONTROL-SYS), as well as all nets assignedvia the run control file and the jobs brought to execution within the nets.

RUN-CONTROL-SYSTEMName of the run control system.

SELECT-TURNUSProcessing cycle (monthly, weekly, daily, etc.), which is always assigned anumeric value. All jobs and conditions whose SEL-TUR is 0 or equal to the SEL-TUR of the net control record are taken into account for processing. SEL-TURis also used as a selection criterion when defining net run variants within theframework of net planning.

SERVER-NAMESERVER-NAME is a symbolic name for the host on which and the user ID underwhich a SV job is to run.

standard netNet description generated by production planning, including all job descriptionsassigned to the net.

static jobs/server jobsJobs/SV jobs in the JMDLIB which may be assigned to two or more nets.

structure elementIndividual element of a net structure for starting a task, editing a condition taskor querying a condition.

380 U5184-J-Z125-7-76

Glossary

symbolic start datesDates for the net start time, assigned when standard nets are generated andprocessed. They are entered in the net parameter PLAN-START. The AVASadministrator enters the symbolic start dates in the calendar and also takescharge of their further management with regard to the calendar. Symbolic startdates are also selection criteria for defining net run variants during net planning.

SYMDAT-NAMEName of a symbolic start date.

SYNC-INDEXSynchronization index in the net description.

taskBS2000 job, SDF-P S procedure or server job (SV job)

temporary jobs/server jobsJobs/SV jobs in the JMDLIB which can be assigned uniquely to a net(with _yymmdd_hhmmss as part of the name).

USERParameter for the ENTER call of the job, the S procedure or the AVAS agentAVSSINCM.

user groupGroup of users who access public AVAS libraries.

USER-PARAM-FILEUser file with current values of the net run parameters.

U5184-J-Z125-7-76 381

Related publicationsPlease apply to your local office for ordering the manuals.

[1] AVAS (BS2000/OSD)Ready Reference

Target groupThe Ready Reference is intended for AVAS users and AVAS administrators.ContentsThe Ready Reference is divided into user and administrator sections, each of whichcontains an overview of the statements and operands, a graphical display of the masksequences and operation codes, and an overview of the net, condition description and logstatuses. It also contains a list of all AVAS messages.

[2] AVAS (BS2000/OSD)Job HandlingUser Guide

Target groupThis manual is addressed to AVAS users.ContentsThe manual contains descriptions of the following: menus and statements used for jobhandling; time scheduling for specific periods; all steps relating to production (planning,preparation, release, execution and monitoring); AVAS reports.

[3] AVAS (BS2000/OSD)for the AdministratorSystem Administrator Guide

Target groupThis manual is addressed to AVAS administrators.ContentsThe manual describes the operations required to set up the AVAS system, frequentlyrecurring administration tasks, the external creation of AVAS elements, the AVAS programinterface, and the AVAS server interface. It also discusses the option of using AVAS inBS2000 multiprocessor mode.

382 U5184-J-Z125-7-76

Related publications

[4] INFORMIX Guide to SQL (UNIX)ReferenceUser Guide

Target groupUsers familiar with the concepts of relational databases.ContentsThis manual describes the structure and contents of the demonstration database that isinstalled with every INFORMIX application development tool. It contains syntax explana-tions of all SQL statements with diagrams and usage instructions and examples. Themanual also provides details on the INFORMIX system catalog as well as on the columndata types supported and on the environment variables used.

[5] FHS (TRANSDATA)User Guide

Target groupProgrammersContentsProgram interfaces of FHS for TIAM, DCAM and UTM applications. Generation, applicationand management of formats.

[6] IFG for FHS (TRANSDATA)User Guide

Target groupTerminal users, application engineers and programmersContentsThe Interactive Format Generator (IFG) is a system that permits simple, user-friendlygeneration and management of formats at a terminal. In conjunction with FHS, theseformats can be used on the host computer. This user guide describes how formats aregenerated, modified and managed, plus also the new functions of IFG V8.1.

[7] BS2000/OSD-BCCommands, Volumes 1-4User Guide

Target groupNonprivileged BS2000/OSD users and systems support staffContentsThis manual contains the BS2000/OSD commands for the basic configuration and selectedproducts. The introduction provides information on command input. With the aid of SDF-P,users of SHOW commands can make use of output in structured S variables, as describedin Volume 4.

U5184-J-Z125-7-76 383


[8] MAREN (BS2000/OSD)for UsersUser Guide

Target groupBS2000 users.ContentsThe MAREN user program allows nonprivileged BS2000 users to manage volumesarchived under their user ID in the MAREN catalog.

[9] SDF-P (BS2000/OSD)Programming in the Command LanguageUser Guide

Target groupThe manual addresses BS2000/OSD users and systems support.ContentsSDF-P is a structured procedure language in BS2000. The introduction is followed by adetailed description of commands, functions and macros.

[10] SDF (BS2000/OSD)Introductory Guide to the SDF Dialog InterfaceUser Guide

Target groupBS2000/OSD usersContentsThis manual describes the interactive input of commands and statements in SDF format.A Getting Started chapter with easy-to-understand examples and further comprehensiveexamples facilitates use of SDF. SDF syntax files are discussed.

[11] SDF (BS2000/OSD)SDF ManagementUser Guide

Target groupThis manual is intended for system administrators and experienced BS2000 users.ContentsIt describes how SDF is installed and administered using SDF commands and the SDF-I,SDF-U and SDF-PAR utility routines. It includes a description of SDF-I, SDF-U andSDF-PAR statements.

384 U5184-J-Z125-7-76


[12] BS2000/OSD-BCUtility RoutinesUser Guide

Target groupThe manual addresses both nonprivileged users and systems support.ContentsThe manual describes the utilities delivered with the BS2000 basicconfiguration BS2000/OSD-BC.

[13] FHS-DOORS (MS-DOS, BS2000)Mask Conversion and Optimization

Target groupThis manual addresses all FHS-DOORS mask optimizers.ContentsThe manual introduces the principles of an FHS-DOORS application. It then describes theconversion of masks using the mask converter, and the optimization of masks using theDialog Builder and the Semantic Editor.

[14] FHS-DOORSUser Guide

Target groupBS2000 users who want the convenience of graphical user interfaces when working withBS2000 applications (UTM).ContentsConverting masks using the mask converter (BS2000). Processing masks with the DialogBuilder (SINIX). Starting an application under FHS-DOORS (SINIX).

U5184-J-Z125-7-76 385

Index

- 36-- 36#AVA# statement 72#AVD# statement 69#AVJ# statement 70#AVM# statement 67#AVS# statement 68(#SCR#) or (#SCR#,n) for output tapes 263(#VOL#) or (#VOL#-n) for input tapes 263*DEL, resetting FREE/NWRK 248+ 36++ 36

AABLDAT 371ABLDUP 371ADD-COND-DESCRIPTION 213adding a record 33AFTER-INDEX 199assigning

mask names 51user mask 67variable fields in masks 51

attribute "production-free" 245automatic restart 371AUTOMATIC=NO 123AUTOMATIC=YES 123AVAS

dialog termination 13in HIPLEX MSCF network 1

AVAS agent AVSSINCM 167AVAS pool 85AVAS report 371AVAS statements

as /REMARK commands 65

386 U5184-J-Z125-7-76

Index

as /WRITE-TEXT commands 65function 66overview 65using 65

AVAS variablesaddressing and modifying 75continuation character 77F# 77N# 77overview 66P# 76rules for server jobs 81S# 75specifying 75using 65

AVAS-DOORSmasks 35resizing masks 37size of masks 35starting 37starting directly 37terminating 38

AVAS-QUER 279CREATE-FORMAT statement 288CSV format 279database 279entering statements 284error handling 300importing data into the database 292INFORMIX database 279LOAD format 279SELECT-OBJECT statement 289SIGNON statement 287software dependencies 300start procedure 282structure of the database 293structure of the output file 284temporary files 300

AVAS-SYSTEM-LIBRARY 371AVAS-USER-LIBRARY 210, 371AVSSINCM

AVAS agent 167

U5184-J-Z125-7-76 387

Index

Bbatch statements 371branch defined 126buttons 36

Ccalendar 371

deleting 258displaying 254modifying 244paging in 251start/end dates 244symdats contained in 244

calendar daydisplaying last 251production-free 248

calendar sectioncopying 249displaying 255modifying start/end dates 250

CALENDAR-NAME 239calender

time period covered 239call

an external element 69call JCL element 68CALLIB 371change

retention period 194change RETENTION-PERIOD 194characteristic for forming net run variants 141CHECK 36CHECK in conjunction with SAVE or EXECUTE 29CMD field (operation) 17CMD field (statement) 20command /REMARK #UID# 264comparison operation 226compatibility 9COND-DOC 157COND-INDEX 158condition 371

earliest time of testing 119external 113in a net description, defining 115

388 U5184-J-Z125-7-76

Index

in status NO-OCCURE 126in status OCCURRED 126JOB 115JVA 115, 119NET 115RESOURCE 115, 117restart variant 118timing control 119VALUE 115, 118

condition control 118condition description 372

defining 112deleting 228displaying 231initializing in ABLDAT 116outputting contents 118setting up 213

CONDITION-JVA-NAME 372CONDITION-TEXT 372CONDITION-TYPE 372CONDITION-VALUE 372COND-JVA-NAME 158COND-NAME 158COND-STATUS

FREE 117SHARE 117

COND-TEXT 158COND-VALUE 159contents

of monitoring job variables 71continuation character

AVAS variables 77CONTINUE 36CONTINUE without effect 33control record

distinguishing characteristic 146control section (mask) 16copy

calendar section 249library elements 207net description 196

COPY-CALENDAR-NAME 257COPY-ELEMENT 207COPY-NET-DESCRIPTION 196

U5184-J-Z125-7-76 389

Index

COPY-NET-NAME 198COPY-TO-CAL-DATE 250coupling AVAS with MAREN 259create

new calendar 238volume lists 266

create net descriptionin NETLIB 130

CREATE-CALENDAR 238CREATE-FORMAT (AVAS-QUER statement) 288CREATE-NET-DESCRIPTION 130

Ddatabase queries for AVAS-QUER 279DATE 247DAY (day of the week) 247days of week generated as symdats 238default values

net parameters 133defining

a new structure element 146condition descriptions 112

defining structure elementsfor starting a job/SV job/S procedure 112

definition of production (job management) 2DELAY-SOLUTION 138, 372

dependence on 139effect 138

deletea record 33calendar 258condition description 228jobs and JCL elements 102net description 205S procedure 102server job 102structure elements 145

DELETE-CALENDAR 258DELETE-COND-DESCRIPTION 228DELETE-DOCUMENT 110DELETE-JOB 102DELETE-NET-DESCRIPTION 205dependency 372

resolved 378

390 U5184-J-Z125-7-76

Index

descriptionof syntax 46

displaycalendar 254calendar section 255condition description 231jobs, S procedures, SV jobs, JCL elements 100last calendar day 251net description 200net parameters 133net structure 143user mask 63

distinguishing characteristiccontrol record 146

DOCLIB 372DOCSYS 372DOCUMENT 36documentation elements

assignment 27, 105deleting 110displaying 18, 108editing 106processing 27

documentation for netsdisplaying 200

EEARLIEST-START 372edit external SAM/ISAM user files 104edit jobs, S procedures, server jobs, JCL elements 95EDIT-DOCUMENT 106editing nets 112EDIT-JOB 95EDT 104

calling under AVAS 104element

copying from external PLAM library 207copying from external SAM file 207entering in JCLLIB with new name 96modified, writing back to JCLLIB 96name structure 42not writing back to JCLLIB 96selecting 21

element name

U5184-J-Z125-7-76 391

Index

fully qualified 21partially qualified 21

element processingaborting 22completing 22continuing 22

element selection 33ELEMENT/GROUP 210empty system masks 104end-of-field mark 77enter

information in the journal file 72ENTER parameters

for jobs/S procedures,global specification 133taking from the /LOGON or /SET-LOGON-PARAMETERS command 133

ENTER-FILE 151, 372entering

net parameters 142net planning data 138NET-PASSWORD 135VSNs for input tapes 263VSNs for output tapes 265VSNs in JCL 263

entering BS2000 parameters for ENTER call 133entering information in the journal 72entering plan data

structure elements with FU=A/M/D, TYPE=RES/VAL 185structure elements with FU=C, TYPE=JVA/NET/JOB/RES/VAL 180, 183structure elements with FU=D and TYPE=NET/JOB 185structure elements with FU=J/P/X, TYPE=STD/MOD/EXT/EXX 176

ENTER-PARAMS 151, 372LOGON 151NET 151

error handling in AVAS-QUER 300EXECUTE 36execution of production (job handling) 2external conditions 113external element

calling 69external SAM/ISAM user files

editing 104EXTERNAL-FILE 211, 373

392 U5184-J-Z125-7-76

Index

Ffile password 151FILE-PASSWORD 151, 373FIRST-CALENDAR-DATE 239format of record

in production job (output record) 76format value assignments F# 78FORMAT-NAME 142, 373FORMAT-TEXT 142FREE 248FREE/NWRK

resetting 248FREE-CALENDAR-DATES 240FROM-DATE 249FROM-INDEX 199fully qualified element name 21FUNCTION 373further processing

input file 274output file 275

Gglobal changes to nets 191

Iidentification

of all jobs in net 136identifier

job⁄S procedure 156IGNORE 36IGNORE without effect 33index level 373index structure element 146information function 30information section (mask) 15input file

further processing 274input parameters

structure elements with FU=A/M/D, TYPE=RES/VAL 173structure elements with FU=C, TYPE=JVA 157structure elements with FU=C, TYPE=NET/JOB/RES/VAL 162structure elements with FU=D, TYPE=NET/JOB 175structure elements with FU=J/P, TYPE=STD/MOD/EXT/EXX 151structure elements with FU=W, TYPE=TIM 175

U5184-J-Z125-7-76 393

Index

structure elements with FU=X, TYPE=STD/MOD/EXT 167input record in job 76interactive mode with AVAS 11interactive prompting 11

JJCL element 373

name of 68JCL statements

executing (#RI) 73interchanging (#RA) 73suppressing (#RU) 73

JCLLIB 373JCLSYS 374JMDLIB 374JMDSYS 374job 374

defining in net description 114earliest start point 119

job control record 374job masks 51job modification

user mask for 52job or JCL element

name (JCLLIB) 96job⁄S procedure

identifier 156JOB-ACCOUNT 152, 374JOB-CAT 152JOB-CLASS 152, 374JOB-DOC 152, 374JOB-INDEX 153, 374JOB-LOG 374JOBLOG 36JOBMAP 374JOB-NAME 153JOB-PARAMETER 153, 374jobs and JCL elements

deleting 102displaying 100

jobs, S procedures, server jobs, JCL elementsediting 95

JOB-SOURCE 153JOB-STATUS 374

394 U5184-J-Z125-7-76

Index

JOB-TEXT 154, 375JOB-TYPE 375journal file 375

entering information 72JRLDAT 375JRNDAT 375JVA-LENGTH 159JVA-PASSWORD 159JVA-POSITION 159JV-LENGTH 375JV-NAME 375JV-PASSWORD 375JV-POSITION 375

LLAST-CALENDAR-DATE 239latest start time

relative to planned start time 139LATEST-OCCURE 119LATEST-START 139, 375LATEST-START expired 138LIFE-TIME 139, 375link names for AVAS-QUER 281list net description, output 200list output creating 356LIST-FILE-NAME 355listing

AVL001 357AVL002 357AVL003 358AVL004 359AVL005 360AVL035 362AVL041 363SHOW-DOCUMENT 362SHOW-JOB 363SHOW-NET-DESCRIPTION 356

listings or logs of data 355LOG 154, 375LOGSYS 375

U5184-J-Z125-7-76 395

Index

MM 376MARENAV 259

messages 276module 259

mark– 33+ 33+/– 19A 33D 33N 23overview 33permitted 21S 21Y 22

maskAVC001 239, 307AVC002 246, 255, 307AVC004 308AVC010 308AVC012 257, 309AVC020 309AVC021 310AVD001 311AVD002 311AVD003 312AVD004 312AVD005 313AVD006 313AVD007 314AVD008 314AVD009 315AVD010 315AVD011 316AVD012 316AVD015 317AVD016 317AVD017 318AVD018 318AVD030 215, 222, 233, 319AVD031 224, 235, 319AVD040 220, 230, 233, 320AVE010 97, 321

396 U5184-J-Z125-7-76

Index

AVE011 98, 321AVF001 322AVF002 322AVF004 323AVF012 323AVF014 324AVI001 325AVI002 325AVI003 326AVI004 326AVI005 327AVI006 327AVI007 328AVI008 328AVI009 329AVI010 329AVI011 330AVI012 330AVI013 331AVI014 331AVI015 332AVI016 332AVI017 333AVI018 333AVI020 334AVM001 335AVM010 335AVM011 336AVM012 336AVM013 337AVM020 337AVN001 133, 338AVN002 151, 338AVN003 157, 339AVN004 143, 189, 339AVN005 199, 340AVN006 142, 340AVN007 193, 341AVN008 162, 341AVN009 167, 342AVN011 187, 192, 202, 342AVN012 198, 343AVN020 343AVN021 176, 344

U5184-J-Z125-7-76 397

Index

AVN022 180, 344AVN023 183, 345AVN024 185, 345AVN030 173, 346AVN031 175, 346AVN032 175, 347AVP001 348AVP003 348AVP010 349AVP011 349AVS010 350AVS011 210, 350AVS015 24, 351AVS016 107, 351AVS019 107, 111, 352AVS020 352AVS025 353AVS030 353delete from net mask table 140, 142for the restart variable 51usage with CREA-NET-DESC 23usage with MOD-NET-DESC 23

mask library 51JOBMAP 63NETMAP 63

mask names 51assigning 51

mask operation 17maximum name lengths 42MODE operand 207MODE=LIBIN 208MODE=LIBOUT 207MODE=SAMIN 208MODE=SAMOUT 208modified statement names 20modify

calendar 244MODIFY-CALENDAR 244MODIFY-COND-DESCRIPTION 217modifying

net description 186structure elements 145

MODIFY-NET-DESCRIPTION 186module MARENAV 259

398 U5184-J-Z125-7-76

Index

monitoring job variablecontents of 71name of 70

multiple selection buttons 36multiple start times specifying 138

Nname

of a JCL element 68of a statement 20of job, S procedure, SV job, JCL element (JCLLIB) 96of monitoring job variable 70of net mask 142of user mask 67

name formatof elements 42

name lengthsmaximum 42

naming conventions 42net 376

copying to "foreign" NETLIB 196defining 112editing 112global changes 191not planned via a calendar 141using calendar to plan 141

net control record 376net description 1, 112, 376

copying 196creating in NETLIB 130defining conditions 115deleting 205displaying 200modifying 186outputting 200saving 132

net description list outputting 200net masks 51net modification

user mask for 52net parameters

default values 133displaying 133entering 142

U5184-J-Z125-7-76 399

Index

net planning dataentering 138

net processing 377net run variants

characteristic for forming 141net structure

displaying 143NET-ACCOUNT 133, 376NET-CAT 133, 376NET-CLASS 134, 376NET-DELAY-SOLUTION 376NET-DOC 134, 376NETLIB 376NET-LOG 134, 376NETMAP 376NET-NAME 376NET-PARAMETER 135, 376NET-PASSWORD

entering 135NET-STATUS 377NETSYS 377NET-TEXT 135, 377NET-TYPE 377NET-TYPE 1 135NET-TYPE 2 136NET-TYPE 3 136NET-USER 136, 377netwide valid user parameters 52NO-OCCURE 117NPRLIB 377

OOBJECT (operand) 186OBJECT operand 186OCCURE-DELAY- SOLUTION 119OCCURE-VALUE 119OK 36operand

MODE 207OBJECT 186

operand name 20operand value 20operation 377operation character 17

400 U5184-J-Z125-7-76

Index

– – 17++ 17+/- 17+n 17? 18, 30–n 17overview 31

operation name 17CHECK 18, 28CONTINUE 18DOCUMENT 18DOCUMENT (using) 25EXECUTE 18FIRST 18IGNORE 18JOBLOG 18LAST 17overview 31PRINT 18, 24RETURN 18SAVE 18

OPR field 20optional settings 128OUT-OF-PLAN report 377output file

further processing 275overview

of marks 33of system masks 305operation characters 31operation names 31

Ppaging functions 17

+/–/FIRST/LAST 21parameter

NEXT=DES 143NEXT=SYM 143

parameter mask selecting 143partial restart 129partially qualified element name 21PERDAT 377performing volume checks 259period 377

U5184-J-Z125-7-76 401

Index

calendar section 245permanently assigned symbolic data entries 245permanently assigned symbolic names 245PLANNED-NET-MODIFICATION report 377planning period 377PLAN-START 140, 378POINT-OF-ERROR 120POINT-OF-RESTART 121

status changes 125positioning the work window 19PRINT 36procedures

displaying 100processing section (mask) 15production definition 2production execution 1, 2production job

format, output record 76production monitoring 1production plan 1, 378production preparation 1

Rreal start time for net 140real/symbolic start times number 140record

adding 33deleting 33

relative symbolic start dates 245relative symbolic start times 245release

for production 1period 378

REPORT generator 378REPORT statements 378resizing masks (AVAS-DOORS) 37resolved dependency 378resolved start time 378restart

automatic 156, 171, 371job 378manual 156, 171multiple 122partial 129

402 U5184-J-Z125-7-76

Index

statement 378through index level 9nn 121with restart statements 155without restart statements 155

restart index 121defining for restart variants 148

restart index level 121restart processing, type of 155restart statement 73

#RA 73#RI 73#RU 74as /REMARK command 74as /WRITE-TEXT command 74canceling processing 74overview 73

restart types 122restart variant

display 124selecting 124specifying 70valid 120

RESTART-IND 148RESTART-INDEX 121, 154, 378RESTART-INDEX=END 121RESTART-JOB-NAME 123RESTART-NAME 155, 378RESTART-NET 378RESTART-SKIP-CONDITION 128RESTART-SKIP-ERROR 128RESTART-TYPE 155, 379RESTART-TYPE=NORMAL 122RESTART-TYPE=RESTART 122RESTART-VARIANT 156, 172, 379RESTART-WAIT-CONDITION 128RESTART-WAIT-ERROR 128RETENTION-PERIOD, changing 194RETURN 36rules for S procedures 79run control file 379run control system 379

assigning 136RUN-CONTROL-SYSTEM 136, 379

U5184-J-Z125-7-76 403

Index

SS procedures

defining in net description 114deleting 102rules for 79

SAVE 36selecting records 33SELECT-OBJECT (AVAS-QUER statement) 289SELECT-TURNUS 379

net description 141task specification 178

server jobsdefining in net description 114deleting 102displaying 100rules with AVAS variables 81

server user ID (login name)symbolic name 172

SERVER-NAME 172, 379SERVER-PASSWORD 172set errors via monitoring job variables 70set restart variant via monitoring job variables 70setting up a condition description 213shift procedure 271SHOW-CALENDAR 254SHOW-COND-DESCRIPTION 231SHOW-DOCUMENT 108SHOW-FORMAT 63SHOW-JOB 100SHOW-NET-DESCRIPTION 200SIGNAL program

start 88terminating 90

signing off from the AVAS system 13signing on to the AVAS system 11SIGNON (AVAS-QUER statement) 287single selection buttons 35software dependencies for AVAS-QUER 300SPECIAL NWRK OR FREE DATES 242specification of restart variant 70standard net 379start date

relative symbolic 245start dates symbolic 380

404 U5184-J-Z125-7-76

Index

start timenone specified 141relative symbolic 245resolved 378specifying multiple 138

start time for netreal 140symbolic 140

start/end datescalendar section, modifying 250

starting AVAS-DOORS 37starting AVAS-DOORS directly 37statements selecting 21static jobs 379static server jobs 379status

after restart 125before restart 125changes in POINT-OF-RESTART 125changes of jobs and conditions 126

storing user mask 51structure element 379

adding 189assigning an index 113condition control via job variables 157defining a new one 146defining for starting a job/SV job/S procedure 112deleting 145, 189for executing server jobs 167minimal specification 143modifying 145, 189type 149type EXT 150type EXX 150type JOB 150type JVA 150type MOD 149type NET 150type RES 150type STD 149type TIM 150type VAL 150WAIT for TIME 119

structure of AVAS system masks 14

U5184-J-Z125-7-76 405

Index

structure of AVAS user masks 50symbolic

permanently assigned data entries 245start dates 238

symbolic name of a server user ID (login name) 172symbolic names permanently assigned 245symbolic start dates 380symbolic start time for net 140symdat±n 141SYMDAT-NAME 380SYNC-INDEX 148, 380

END 148index 148NXT 148

syntax description 46system masks

empty 104overview 305structure of 14

SYSTEM symdat 238default names 239

system variables S#overview 75

SYSTEM-SYMDAT-NAMES 242

Ttape for user ID reserving 265tape mount listing 270task 380temporary files for AVAS-QUER 300temporary job 380temporary server job 380terminating AVAS-DOORS 38time scheduling 1time scheduling via calendar 237timing control for conditions 119TO-DATE 249TO-INDEX 199TRANSFER program

starting 91terminating 92

transport list 268type

of day of the week 241

406 U5184-J-Z125-7-76

Index

type of restart processing 155type of the structure elements 149

Uupdating CMD field 20updating OPR field 20USER 156, 380user group 380user ID reserving tape for 265user mask

assigning 67different 50displaying 63example 53example (IFG) 57for job modification 52for net modification 52having same name 63name of 67storing 51structure of 50

user parametersvalid netwide 52

USER symdat 238USER-GROUP=$ug 209USER-PARAM-FILE 77, 380

Vvalid restart variants 120value assignments for F#

format of 78variable fields in masks

assigning 51variable values

inclusion, in production job 76volume checks, performing 259volume lists, creating 266VSN

enter for input tapes 263enter for output tapes 265enter in JCL 263in a net, further processing 272

U5184-J-Z125-7-76 407

Index

Wwildcard (#SCR#) 265wildcard (#VOL#) 263work window 17working with masks 17


U5184-J-Z125-7-76 409

Contents1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Brief product description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 Summary of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4 Changes since the last version of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.5 Notes on upgrading from AVAS V3.0A to AVAS V4.0A . . . . . . . . . . . . . . . . . . . . . . . . . . 81.6 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Interactive prompting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Interactive mode with AVAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1.1 Signing on to the AVAS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1.2 Calling AVAS system statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.1.3 Signing off from the AVAS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2 Mask structure and operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.1 Structure of AVAS system masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.2 Working with masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Selecting statements and elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Using the PRINT operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Using the DOCUMENT operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Using the CHECK operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Information function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Overview of the operation names, characters and marks . . . . . . . . . . . . . . . . . . . . . . . 31

2.3 AVAS-DOORS - graphic interface for AVAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34General description of the AVAS-DOORS masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34User-defined masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Calling EDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Increasing and reducing the size of AVAS-DOORS masks . . . . . . . . . . . . . . . . . . . . . . 37Starting and terminating AVAS-DOORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.4 Naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.4.1 Entry of partially qualified element names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.4.2 Wildcards in user groups and element names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.4.3 Syntax description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

410 U5184-J-Z125-7-76

Contents

3 Creating jobs/S procedures/server jobs, documentation elements and nets . . . . 493.1 Creating the AVAS user masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

User masks for net modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52User masks for job modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52SHOW-FORMATDisplay user mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

3.2 AVAS statements and variables in jobs, S procedures, server jobs and JCL elements . 653.2.1 AVAS statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

#AVM# - Assign user mask for run parameter input . . . . . . . . . . . . . . . . . . . . . . . . . . . 67#AVS# - Call JCL element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68#AVD# Call external element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69#AVJ# - Set errors and restart variant via task job variables . . . . . . . . . . . . . . . . . . . . . 70#AVA# Enter information in journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Statements for restart case #Rx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

3.2.2 AVAS variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.2.3 Transferring runtime logs to AVAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Starting and terminating the SIGNAL program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Starting and terminating the TRANSFER program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Notes on the control parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

3.3 Editing jobs, S procedures, server jobs and JCL elements . . . . . . . . . . . . . . . . . . . . . . 95EDIT-JOBEdit jobs, S procedures, server jobs and JCL elements . . . . . . . . . . . . . . . . . . . . . . . . 95SHOW-JOBDisplay jobs, S procedures, server jobs and JCL elements . . . . . . . . . . . . . . . . . . . . . 100DELETE-JOBDelete jobs, S procedures, server jobs and JCL elements . . . . . . . . . . . . . . . . . . . . . 102EDTEdit external SAM/ISAM user files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

3.4 Editing documentation elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105EDIT-DOCUMENTEdit documentation elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106SHOW-DOCUMENTDisplay documentation elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108DELETE-DOCUMENTDelete documentation elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

3.5 Editing nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123.5.1 Defining jobs, S procedures and server jobs in a net description . . . . . . . . . . . . . . . . 1143.5.2 Defining conditions in a net description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153.5.3 Preparing for the restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

U5184-J-Z125-7-76 411

Contents

3.5.4 Statements for net editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130CREATE-NET-DESCRIPTIONCreate net description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130MODIFY-NET-DESCRIPTIONModify net description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186CHANGE-NET-DESCRIPTIONGlobal changes to nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191COPY-NET-DESCRIPTIONCopy net description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196SHOW-NET-DESCRIPTIONDisplay net description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200DELETE-NET-DESCRIPTIONDelete net description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

3.6 COPY-ELEMENTCopy library elements from/to external file or library . . . . . . . . . . . . . . . . . . . . . . . . . . 207

4 Condition descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213ADD-COND-DESCRIPTIONAdd condition description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213MODIFY-COND-DESCRIPTIONModify condition description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217DELETE-COND-DESCRIPTIONDelete condition description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228SHOW-COND-DESCRIPTIONDisplay condition description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

5 Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237CREATE-CALENDARSet up new calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238MODIFY-CALENDARModify calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244SHOW-CALENDARDisplay calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254COPY-CALENDARCopy calendar with symbolic dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256DELETE-CALENDARDelete calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

6 Coupling AVAS with MAREN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Performing volume checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Entering VSNs in the JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Creating volume lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

412 U5184-J-Z125-7-76

Contents

7 AVAS-QUER utility routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2797.1 Working with AVAS-QUER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2817.1.1 Prerequisites for starting AVAS-QUER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2817.1.2 Starting AVAS-QUER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2827.1.3 Entering statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2847.1.4 Terminating AVAS-QUER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2847.1.5 Structure of the output file(s) created by AVAS-QUER . . . . . . . . . . . . . . . . . . . . . . . . 2847.2 AVAS-QUER statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Standard SDF statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286SIGNONLog in to AVAS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287CREATE-FORMATSelect output file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288SELECT-OBJECTSelect AVAS objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

7.3 Data storage for AVAS-QUER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2927.3.1 Creating the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2927.3.2 Importing the data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2927.3.3 Structure of the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2937.3.4 Structure of the database tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2947.3.5 Sample database queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2977.4 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3007.5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3007.6 AVAS-QUER messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

8 Masks for job management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

9 Listings for job management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3559.1 SHOW-NET-DESCRIPTION listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3569.2 SHOW-DOCUMENT listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3629.3 SHOW-JOB listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

List of statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

List of masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

U5184-J-Z125-7-76 413

AVAS V4.0A (BS2000/OSD)

Job Management

Target groupThis manual is addressed to AVAS users.ContentsThe manual contains descriptions of the following: menus and statements used for jobmanagement; the creation of jobs/S procedures and nets, condition descriptions, andcalendars; the coupling of AVAS with MAREN; the AVAS-QUER utility routine.

Edition: June 1998

File: AVAS_AVW.PDF

BS2000 is a registered trademark of Siemens Nixdorf Informationssyteme AG.

Copyright © Siemens Nixdorf Informationssysteme AG, 1998.

All rights, including rights of translation, reproduction by printing, copying or similarmethods, even of parts, are reserved.

Offenders will be liable for damages. All rights, including rights created by patent grant orregistration of a utility model or design, are reserved.

Delivery subject to availability; right of technical modifications reserved.

Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Compu-ters. This new subsidiary of Fujitsu has been renamed Fujitsu Technology So-lutions.

This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed.

Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.

Contact and support addresses will now be offered by Fujitsu Technology So-lutions and have the format …@ts.fujitsu.com.

The Internet pages of Fujitsu Technology Solutions are available at http://ts.fujitsu.com/... and the user documentation at http://manuals.ts.fujitsu.com.

Copyright Fujitsu Technology Solutions, 2009

Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seit-dem den Namen Fujitsu Technology Solutions.

Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion.

Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.

Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Form …@ts.fujitsu.com.

Die Internetseiten von Fujitsu Technology Solutions finden Sie unter http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die Benutzerdokumentation.

Copyright Fujitsu Technology Solutions, 2009

Documents

AVAS V4.0A Job Management - Fujitsu Technology Solutionsmanuals.ts.fujitsu.com/file/976/avas_avw.pdf · The "AVAS Ready Reference" [1] contains an overview of the statements and operands,