TDS Administrator s Guide (Ref: 47 A2 32 UT) TILS User s Guide (Ref: 47 A2 04 US) SBR User s Guide (Ref: 47 A2 03 US) The post-simulation phase

Transcription

1

2

3 February 2000

4 0

5 Preface Scope and Purpose Prerequisites This guide describes the procedure for the installation of Version 5 of the SIM7 product and how to use it to simulate the load of a real-time TDS application. The reader is assumed to be familiar with the TDS, TILS and SBR products and may like to refer to the following documentation for more ample information. TDS Administrator s Guide (Ref: 47 A2 32 UT) TILS User s Guide (Ref: 47 A2 04 US) SBR User s Guide (Ref: 47 A2 03 US) Structure Chapter 1: Chapter 2: Chapter 3: Chapter 4: Chapter 5: Chapter 6: Chapter 7: Chapter 8: Chapter 9: Overview The collection phase The preparation phase The installation phase The builder phase The pre-simulation phase The simulation phase The post-simulation phase Methodology limits Chapter10: Some important recommendations Chapter 11: The TILS logfile Appendix 47 A2 8UR Rev00 iii

6 Simulation of a TDS application with SIM7 (V5) User s Guide iv 47 A2 8UR Rev00

7 Table of Contents 1. Overview 2. The collection phase 2.1 Preparation of the collection phase on a customer site Modification of the Source member of the TDS Modification of the JCL for the TDS step Installation of the After Journal The collecting of information Collecting information "before" the start of the TDS session Collecting information during the TDS session Collecting information "after" the TDS session Summary of information required by the simulation phase The preparation phase 3.1 Description of the user journal file Sorting the user journal file The installation phase 4.1 Installation of the SIM7 MI Installing the SIM7 product The builder phase 5.1 The SIM7 input file SIM7 time management and parameters Parameters Time Management A2 83UR Rev00 v

8 Simulation of a TDS application with SIM7 (V5) User s Guide 5.3 SIM7 output files UFAS files SL Library Members The SIM7 job SIM7 Program errors Authorisation Checks Errors in parameters Unrecoverable errors during processing of the User Journal file Recoverable errors during processing of the User Journal file End of the SIM7 Program SIM7 Limits The pre-simulation phase 6.1 Preparation of the TILS scenario set(s) Preparation of the SIM7_JCLi member(s) Checking of SIM7_DECLARATIONi and SIM7_CORRESPONDENTp System preparation for the simulation phase Restoring the customer data files Checking the file options of the user files Modification of the SITE.CATALOG Preparation of the TDS Modification of CRNETGEN Generation of the TDS Modification of the SITE.STARTUP Modification of the JCL containing the TDS step The simulation phase 7.1 Activation of an SBR collect Activation of the TDS job ACTIVATION OF THE TILS SIMULATION Connection of TILS users Case where connection requests are in the SIM7_DECLARATIONi Case where connection requests are in the SIM7_OCLp The workload Stopping the simulation Stopping the SBR collect vi 47 A2 83UR Rev00

9 7.8 Restoring user files to the "BEFORE" state The post-simulation phase 9. Methodology limits 10. Some important recommendations 11. The TILS logfile A. Appendix A.1 Description of user journal records... A-1 A.2 Messages for errors detected in SIM7 parameters... A-5 A.3 First type of unrecoverable error messages... A-8 A.4 Second type of unrecoverable error message...a A2 83UR Rev00 vii

10 47 A2 83UR Rev00 viii

11 1. Overview SIM7 builds one or several TILS scenarios from information gathered during a previous TDS session. These scenarios may then be used to simulate (replay) the TDS load on either the same system on which the TDS was run or on another system. The gathered information comes from input messages, connection and disconnection data as recorded by the TDS session in its USER JOURNAL. TILS is the Transactional and Interactive Load Simulator and is a standard product of GCOS7. The version 5 of SIM7 supports simulations on systems with large memory sizes running under either GCOS7 V6, V7 or V8. The transactional application to be recorded must run on a GCOS 7-V6, V7 or V8 system. The use of SIM7 is authorised only if one of the following MIs is present: PSBD006 (a Service MI on AP/HPS/EXMS systems) or SCU3633 (a Product MI on AP/HPS systems) or UTSD006 (a Product MI on EXMS systems). It is possible to build and simulate several TDS applications on the same site. The simulation of one TDS application with SIM7 requires 7 phases. The Collection Phase This is the first phase. It consists of: modifying the TDS in order to trigger the recording of input messages, connection, disconnection and break information in the TDS User Journal; saving the data files of the TDS application to be simulated in their initial state (i.e. before starting the TDS session); saving the whole environment of the TDS application (SL, CU, SM & LM libraries, FORMS files...); activating the TDS which will then start recording session information in its User Journal; 47 A2 83UR Rev00 1-1

12 Simulation of a TDS application with SIM7 (V5) User s Guide stopping the TDS after a representative period of time; saving to tape the User Journal records extracted from the After Journal using the DUMPJRNL utility. IMPORTANT: With SIM7 V5 the collection must be realised under GCOS 7-V6, V7 or V8. The Preparation Phase This phase prepares the input to the SIM7 program. This input is obtained by sorting the output from the DUMPJRNL utility according to user-name and time fields. The Installation Phase This phase installs on the system where the simulation is to take place, the libraries specific to SIM7. This is a good time to check that either the MI PSBD006 or the MI SCU3633/UTSD006 is installed. The Builder Phase Two very important notions need to be introduced here: the "simulation set" and the "set identifier". A Simulation Set represents the full environment of a TILS step that would allow the simulation of a part or the whole of a TDS session. Because of the internal limits of TILS, one collected TDS session may have to be split up into one or several simulation sets. One simulation set always requires a UFAS file (the TILS scenario file), and several library members (one of them is the TILS declaration file, another contains JCL to activate the TILS step). Several collected TDS loads may be represented by one or more simulation sets for each TDS load. A Set Identifier is a letter or a single-digit number chosen by the user. This is used as the suffix for the names of all the elements of a simulation set (the scenario file, library members, the TILS command name...) A set identifier must be unique on a given system: all set identifiers for one TDS must be different; all set identifiers for all the TDS to be simulated on a same system must be different; The SIM7 program is run during this phase. It will automatically build the simulation set(s) for one collected TDS session A2 83UR Rev00

13 Overview After checking the validity of the MI, it reads the whole of the sorted User Journal and calculates the number of simulation sets necessary to simulate the real TDS load. It then builds the UFAS file(s) containing scenario programs for all the TILS users (one per simulation set); SL library member(s) containing the TILS declaration file(s) (one per simulation set); SL library member(s) containing the JCL to activate the TILS step(s) (one per simulation set); SL library member containing commands for CATMAINT to insert the TDS users into the SITE.CATALOG of the system where the simulation is to be enacted (one for all the simulation sets of one TDS); The Pre-Simulation Phase This phase involves checking the simulation sets created and adapting certain elements to the simulation system in order to obtain correct behaviour of the simulation phase. The Simulation Phase Here the TDS is launched with the environment restored from the one previously saved during the Collection Phase. SIM7 JCL created during the Builder Phase are then activated and the TILS simulation begins. All users are automatically connected and their input messages obtained from the User Journal during the Collection Phase are re-sent. The Post-Simulation Phase In this last phase the SIM7 administrator analyses the results of the simulated session and compares them to those of the original one. 47 A2 83UR Rev00 1-3

14 Simulation of a TDS application with SIM7 (V5) User s Guide A2 83UR Rev00

15 2. The collection phase 2.1 Preparation of the collection phase on a customer site The following steps must be executed in the order given in order to obtain in the TDS User Journal, all the information on the TDS session that is going to be needed by the SIM7 program to generate the files for a TILS simulation later on Modification of the Source member of the TDS Add the following 4 statements to the STDS member. USER-JOURNAL WITH INPUT MESSAGE LOGGING. USE DEVICE-HEADER-LOGGING. USE CONNECTION-LOGGING. USE TILS-SIMULATION. The four statements are described in chapter 2.1. of the TDS Administrator s Guide. The third statement causes connection and disconnection information to be recorded in the TDS User Journal. The fourth statement allows the recording in the User Journal of the actual time of the input message. This is useful when simulating cases of internal aborts of commitment units. With this statement, the name of the user 12 characters long (instead of 8) is also recorded. Note that the last 3 statements must be inserted in the order as indicated in the TDS manuals. After having modified the STDS member run a TP7GEN. 47 A2 83UR Rev00 2-1

16 Simulation of a TDS application with SIM7 (V5) User s Guide Modification of the JCL for the TDS step Add the following statement(s) to the JCL for the TDS step. $ASSIGN USERJRNL, DUMMY; $ASSIGN USERJRNL,JOURNAL=AFTER; if no files are protected by the After Journal This statement is described in the TDS Administrator s Guide Installation of the After Journal The After Journal must be installed on the site if it has not already been installed, as the User Journal is part of the After Journal. For installation procedures, refer to the "File Recovery Facilities User s Guide". The precise space requirements for the User Journal can be calculated as follows: 182 bytes per connection/disconnection 553 bytes per exchange (for an average length of an input message of 100 bytes and 2 SENDs per TPR). As an example, to record a 3-hour session with 200 connections and a load of 2 exchanges per second, the space required would be 11.5 Mbytes. 2.2 The collecting of information Collecting information "before" the start of the TDS session Before activating the TDS step a session of which is to be recorded, save all the user files that are going to be used by the TDS; save all off-line files, TPR SM libraries, CU libraries containing programs that are linked with the TDS (USE procedures) etc. ; run a CATLIST of all private catalogs used by the TDS in order to obtain journalisation and sharing options of all user files. If the TDS job contains several steps, then the above must be done just before the TDS step itself A2 83UR Rev00

17 The collection phase Collecting information during the TDS session When everything is ready, the collecting of information can begin. start an SBR COLLECT (on tape) with all options (LEVEL=DETAILED TDS=1 UFAS=1 SNAPMM=1 SNAPIC=1 MSC=1). start the TDS session with a COLD RESTART. This may be obtained either from a TTDS MODE=COLD command for the previous session, or by the OPTIONS= COLD parameter in the step statement of the TDS JCL. During the TDS activity, user connection, disconnection and dialog information is recorded in the User Journal. After a REPRESENTATIVE period of time, stop the TDS with TTDS MODE=COLD command. stop the SBR COLLECT with the TSBR command. WARNING: the collection period must not span midnight. the use of Pass Thru, either to IOF or to another application is restricted. the use of XCP1 verbs is restricted. the concurrent use of the TDS files by a BATCH program in update mode is restricted. no tests must be made by TPRs on either the system name or the date (during the simulation on day D2, processing is done on files recorded on day D1, the day of the collection phase). no tests must be made by TPRs on the terminal identifier (the TERMINAL- ID of the LOGON TRANSACTION-STORAGE for example) for outward connections. there must be no connection of users during the TDS STARTUP transaction. there must be no conversation with WAIT-TIME within the STARTUP transaction. particular attention must be paid to sites installed with SECUR ACCESS as, for security reasons, the SECUR ACCES password is not logged in the User Journal. In such a case, the TILS users representing real users will not be able to be connected to the application. Contact the service center for a solution to avoid the problem. 47 A2 83UR Rev00 2-3

18 Simulation of a TDS application with SIM7 (V5) User s Guide Collecting information "after" the TDS session Activate the DUMPJRNL utility (cf. document "File Recovery Facilities User s Guide") to retrieve from the After Journal and store in an output file all the events recorded in the User Journal by the TDS. For example, DUMPJRNL TDS=tdsname,OUTFILE=customer-user-journal-file, BEGDATE=[YY]YY.MM.DD/HH.MM; The Output file is a UFAS sequential file with the following characteristics: RECSIZE = 8276 CISIZE = 8288 RECFORM = V Refer to paragraph for the evaluation of its size. The value obtained must be adapted bearing in mind that a CI cannot contain more than 255 records. Save this file to tape. It will be used as input to the "SIM7" program to build the TILS scenario and declaration files. 2.3 Summary of information required by the simulation phase the tape containing the file extracted from the User Journal by the DUMPJRNL utility. the tape containing the SBR file or the output from a LOAD_FILE_TO_TAPE of the SBR disk file. the JOR of the TDS session. the save of the <tdsname>.sllib (for the STDS member). the save of the libraries containing the TP7PREP, TP7GEN JCL for the TDS noting the members to use for all these jobs. the save of the libraries containing the JCL activated by CALLs to "SUBJOB" from the TDS. If these JCL activate programs that update the TDS files, then the save of the LM libraries containing these programs and of all other files used by these programs must also be provided. the save of the CU libraries containing the compile units declared in the USE procedures clause of the TDS. the save of all user data files. the save of all the TPR SM libraries. the CATLIST of private catalogs attached to the TDS A2 83UR Rev00

19 The collection phase a LIST_VOLUME of all disks involved (for the evaluation of disk space requirements). the name, project and billing of the master user of the TDS. the PRLOGC listing of the live session. the JOR of the SBR COLLECT of the live session. 47 A2 83UR Rev00 2-5

20 Simulation of a TDS application with SIM7 (V5) User s Guide A2 83UR Rev00

21 3. The preparation phase 3.1 Description of the user journal file Appendix 1 provides a description of the User Journal records used by SIM Sorting the user journal file The User Journal data used as input to SIM7 must be sorted according to user name and time within each user record. Only the records with types "11" to "17" are used by SIM7 (the type is indicated by the first 2 characters of each record). Run a SORT on the Output file of the DUMPJRNL utility according to the following sorting keys: the first sort key is the user name with key position 35 and key length 12. the second sort key is the time with key position 18 and key length 4 and the SBIN attribute. 47 A2 83UR Rev00 3-1

22 Simulation of a TDS application with SIM7 (V5) User s Guide Here is a model of a SORT job. SORT INFILE=customer-user-journal-file OUTFILE=sorted-user-journal-file COMFILE=*A; $INPUT A; RECORD: KEYS = (35,12) (18,4,SBIN) INCLUDE = (1,2) EQ 11 INCLUDE = (1,2) EQ 12 INCLUDE = (1,2) EQ 13 INCLUDE = (1,2) EQ 14 INCLUDE = (1,2) EQ 15 INCLUDE = (1,2) EQ 16 INCLUDE = (1,2) EQ 17 END: $ENDINPUT; A2 83UR Rev00

23 4. The installation phase 4.1 Installation of the SIM7 MI SIM7 is protected by a key. Ensure that either the MI PSBD006 or SCU3633/UTSD006 is installed before activating the SIM7 load module otherwise the following message will appear: SIM7 MI NOT INSTALLED OR SIM7 PROGRAM EXECUTION IS NO LONGER AUTHORIZED CONTACT THE SERVICE CENTER 4.2 Installing the SIM7 product SIM7 Version 5 is delivered on a tape or a cartridge. To install it enter the command: EJR INFILE=INSTALL_SIM7:SIM7V5:dvc-class A Job "INSTALL" is started which: creates an auto-attachable catalog called SIM7.CATALOG if it does not already exist. allocates an SL library called SIM7.SLLIB if it does not already exist. allocates an LM library called SIM7.LMLIB if it does not already exist. moves the "SIM7" load module from the tape to the SIM7.LMLIB and will replace an existing member if any. moves the "SIM7" JCL member from the tape to SIM7.SLLIB and will replace an existing member if any). The "INSTALL" job dialogues with the user to obtain the media name and device class of disks on which to build the libraries and the name of the SIM7.CATALOG owner. 47 A2 83UR Rev00 4-1

24 Simulation of a TDS application with SIM7 (V5) User s Guide A2 83UR Rev00

25 5. The builder phase It is here that the SIM7 Job is run. The SIM7 JCL supplied in the SIM7.SLLIB must be given appropriate values. This chapter will explain the environment necessary for SIM7 activation - the input and output files, parameters etc.. It must be read before starting the SIM7 job for the first time. Section 5.4 shows how to use the SIM7 JCL. Let us recall the two new important notions: "simulation set" and "set identifier". A Simulation Set represents the full environment of a TILS step that would allow the simulation of a part or the whole of a TDS session. Because of the internal limits of TILS, one collected TDS session may have to be split up into one or several simulation sets. One simulation set always requires a UFAS file (the TILS scenario file), and several library members (one of them is the TILS declaration file, another contains JCL to activate the TILS step). Several collected TDS loads may be represented by one or more simulation sets for each TDS load. A Set Identifier is a letter or a single-digit number chosen by the user. This is used as the suffix for the names of all the elements of a simulation set (the scenario file, library members, the TILS command name...) A set identifier must be unique on a given system: all set identifiers for one TDS must be different; all set identifiers for all the TDS to be simulated on a same system must be different; SIM7 will automatically build the simulation set(s) of one collected TDS application. 5.1 The SIM7 input file This is the file that was prepared during the Preparation Phase containing the sorted User Journal data. The IFN associated with this file is "USERJRNL". 47 A2 83UR Rev00 5-1

26 Simulation of a TDS application with SIM7 (V5) User s Guide 5.2 SIM7 time management and parameters Parameters The parameters to be passed to the step SIM7 are keyword parameters inserted in an input enclosure assigned to IFN = "SIM7_I". Parameters are inserted according to the following rules. There must be only one parameter per line or record; The sign "=" must appear between the keyword and its value; A parameter associated with a blank argument or equal to "NIL" is considered as missing; Blanks are authorised at the beginning of a line, at the end of a line and before/after the "=" sign. The line may or may not be terminated by a ";" (semicolon); Parameters may appear in any order ; Parameters that are mandatory whatever the TDS application are as follows: TDSNAME: 4 characters maximum; name of the TDS to be simulated. MASTER: 12 characters maximum; name of the master terminal used in the live TDS session. These characters must be filled with the special value "MBXMBXMBXMBX" if the master terminal was connected to a TDS master mailbox (MASTER MAILBOX IS present in TDS source generation). SIMUSITE: 4 characters maximum; name of the site where the simulation phase is going to take place. PROJOPER: 12 characters maximum; main operator project name under which the master user of the simulated TDS, must be connected (case without master mailbox). If possible, this parameter must be set to the project name under which the master was connected during the live TDS session. In the case of a master mailbox (when MASTER is equal to "MBXMBXMBXMBX") this parameter is optional and is ignored. TDSVERSS: 2 characters (= "V6", "V7" or "V8"); GCOS7 version of site where the simulation is going to occur. Be careful: if TDSVERSS= V7, parameter SIMUV7TS is mandatory. TDSVERSC: 2 characters (= "V6", "V7" or "V8"); GCOS7 version of site where the collect occurred. SETID1: 1 character (chosen from "A" thru "Z" and "0" thru "9"); identifies the first (or only) simulation set of the collected TDS. This set identifier will be used to create a TILS mailbox name for use during the A2 83UR Rev00

27 The builder phase simulation. If we were to give the value "i" to the setid, the mailbox name created would thus be "SIMi". The resulting name must not already exist in VCAM. If so, change the setid value. The same setid will also be used to suffix file names created for the given simulation set. SETMD1: media name of the disk where the scenario UFAS sequential file called SIM7.SCENi, associated with the first (or unique) simulation set of the collected TDS will be created. SETDVC1: device class of the above disk media. Accepted values are: MS/D500, MS/M500, MS/B10, MS/FSA. OCLINTLS: 1 character ( "Y(es)" or "N(o)"); option "Y" to have the OCL statements inserted at the end of the SIM7_DECLARATIONi member; option "N(o)" to leave them in the SIM7_OCLi member of LIBJCL. How to choose this parameter: If you are using SIM7 for the first time, it would be better to choose the option Y as this option provides the best time management at the beginning of the simulation. However, if SIM7 calculates that the complete TDS simulation requires more than one simulation set, it will change the option to the value "N", and the message "** OCLINTLS CHANGED TO N BY SIM7 PROGRAM" will be sent to the user. The reason for this change is that the Time Management cannot be correct if connection requests are spread across all the declaration members of the simulation sets. if SIM7 does not change the value, (case of a TDS simulation with only one set), an abort with RC=SPACEOV from OPRTR can occur when the TILS step is started at the beginning of the simulation (see also chapter 7.1.1). In this case, the option for OCLINTLS must be changed to N and the SIM7 program re-executed. Parameters dependant on the TDS application to be simulated: SETIDn: 1 character (chosen from "A" thru "Z" and "0" thru "9") where n is [2 <= n <= 36]. This identifies the nth simulation set; n must be different to the set identifiers of all the simulation sets for a same TDS and to all the set identifiers of all the simulation sets for other TDS applications to be simulated on the same system. It is possible to have up to 36 simulation sets for one TDS. However SIM7 will only build the simulation sets necessary for the simulation of the TDS identified by "TDSNAME". The message "-----> nn SET(S) WILL BE BUILT BY PROGRAM SIM7" is sent to the user and to the JOR indicating the number "nn" of simulation sets that SIM7 will build. The corresponding SETMDn and SETDVCn must also be specified. Refer to SETID1. 47 A2 83UR Rev00 5-3

28 Simulation of a TDS application with SIM7 (V5) User s Guide SETMDn: where n is [2 <= n <= 36]; media name of the disk where the scenario UFAS sequential file, SIM7.SCENi, of the nth simulation set is to be created if necessary. SETIDn and SETDVCn must also be specified. SETDVCn: where n is [ 2 <= n <= 36]; device class of the above media. SETIDn and SETMDn must also be specified. Accepted values are: MS/D500, MS/D500, MS/B10, MS/FSA. MINTIME: 4 characters long, giving hours (2 characters), and minutes (2 characters). This parameter specifies the time from which records of the User Journal will be taken into account (MINTIME value included). It could be set, for example, to the start time of the TDS step of the collected session, or the time of the message "TDS READY", or the time of the first record or of the first input message found in the unsorted User Journal file. If this parameter is not specified, the default value of MINTIME will be 5 minutes before the earliest time recorded in the User Journal. Refer to paragraph "TIME MANAGEMENT BY SIM7" later on in this chapter for more explanations on how to use this parameter. MAXTIME: 4 characters long, giving hours (2 characters), and minutes (2 characters). This parameter specifies the time up to which the records of the User Journal will be taken into account (MAXTIME value not included). If this parameter is not given, all records with a time later than MINTIME will be extracted. MASTSIMU: up to 12 characters maximum. The main operator user name with which the MASTER user of the simulated TDS will be connected (case without a MASTER mailbox). If this parameter is not specified, the name of the TDS master will be the same as that of the collected TDS session (name given in the MASTER parameter). LOADFACT: 1 or 3 characters representing a number from 0.1 to 5.9 inclusive. The values 1, 2, 3, etc. can be specified as either 1, 2, 3,.. or 1.0, 2.0, 3.0,... This number corresponds to the load multiplication factor to be used for the simulation. The time interval declared is divided by the value of LOADFACT in order to replay the same load more quickly if LOADFACT > 1 or more slowly if LOADFACT < 1. If this parameter is not given the default value of 1 is applied. Parameters dependant on the Release/Technical Status of the simulation site. SIMUV7TS: 4 characters representing the Technical Status running on the V7 simulation site. It can be equal to This parameter is MANDATORY when TDSVERSS= V7. Refer to Section 5.4 for more details on the SIM7 JCL A2 83UR Rev00

29 The builder phase Time Management A further explanation of time management effected by the TILS simulation is necessary. It does not work with the real input time as recorded by the collected TDS. SIM7 time management is based upon relative times. Consider an event E1 (connection, disconnection, input message, break) which took place at time T1 during a collected TDS session. Next consider TO as the time of origin of the collected session (MINTIME value). Then the time at which event E1 occurred will be equal to the time(t1 - TO) relative to this origin. Now consider the simulation phase activated on another day at time TS where TS is the TILS reference time corresponding to the time of the execution of the first TILS command of a TILS step and can have any value in comparison to TO). The event E1 will be activated at a time of day equal to TS + (T1 - TO). If a value "L" different from 1 has been given for parameter LOADFACT, the event E1 will be activated at a time of day equal to TS + (T1 - T0) / L. EXAMPLE: Case where the TDS of the collected session was started at 06h00, where the first output message arrived at 06h08 and where the first input message or connection arrived at 08h22 (refer to appendix 1 for a description of the records of the User Journal). If MINTIME for the simulation is equal to 0600 (or 0603,earliest time minus 5, by default), it means that the first input message or connection will be replayed 2 hours and 22 minutes (08h22-06h00) (or 2 hours and 19 minutes by default) after the first OCL statement of the TILS simulation (TS time). If MINTIME is equal to 0815, the first input message or connection will be replayed 7 minutes (08h22-08h15) after the first OCL statement of the TILS simulation (TS time). Therefore correct calculation of this origin could save time at the beginning of the simulation. The time, in milliseconds, is present in bytes 18 to 21 (4 bytes) of each record from the beginning of the day. 47 A2 83UR Rev00 5-5

30 Simulation of a TDS application with SIM7 (V5) User s Guide 5.3 SIM7 output files IMPORTANT: In the following, the value "i" refers to the set identifier. The value "p" corresponds to the set identifier associated with the first simulation set of a TDS: parameter SETID1 (the value of "p" is equal to the value of "i" for the first simulation set of a TDS) UFAS files IFN = SCEN: cataloged UFAS sequential file dynamically assigned by the program to EFN "SIM7.SCENi" containing the TILS scenario program. There is one scenario file per simulation set. This file is preallocated with an optimised size calculated by SIM7. If it already exists, it is first deallocated. If not enough space is available on the specified disk for the construction of the file, the message sent before any attempt to allocate a SIM7.SCENi file: SIM > PREALLOC OF SIM7.SCENi SIM > SIZE= nnn CI, CISIZE= mmmm will allow the exact size required for the file SIM7.SCENi to be calculated SL Library Members IFN = LIBDECL: existing cataloged library which will contain the SIM7_DECLARATIONi and SIM7_CORRESPONDENTp members. SIM7_DECLARATIONi: is the declaration file as required by the step TILS. There is one declaration member per simulation set. SIM7_CORRESPONDENTp: is permanent if useful information is written to it during a SIM7 step (in all other cases, the member is deleted at the end of SIM7 step). It contains the CRNETGEN commands to be added to the CRDIR member, to allow management of outward connections from the TDS during the simulation phase. There is one correspondent member for all the simulation sets of one TDS. These two members are opened in output mode. IFN = LIBJCL: an existing library which will contain JCL members SIM7_JCLi, SIM7_CATp (and SIM7_OCLp if required) A2 83UR Rev00

31 The builder phase SIM7_JCLi: contains a JCL program to allow activation of the TILS step for the simulation phase. This member must be adapted to the simulation site (jobid, class, etc.). There is one such SIM7_JCLi member per simulation set. SIM7_CATp: contains CATMAINT statements for the creation of Projects, Billings and Users to be used during the simulation phase. Its contents must match up with the existing SITE.CATALOG and a $JOB and CATMAINT statements may have to be added to make an effective JCL member. There is one SIM7_CATp member for all the simulation sets of one collected TDS. SIM7_OCLp: This member can be permanent or temporary. It contains EXDIR statements with connection descriptions for TILS to start groups of TILS users declared in SIM7_DECLARATIONi. Temporary or permanent options are given by means of the OCLINTLS parameter of the SIM7 step (cf. chapter 6.2). If the member is declared temporary, its contents are appended to the end of the SIM7_DECLARATIONi member when the SIM7 program terminates. If the permanent option is chosen, there is one OCL member for all the simulation sets of one TDS. IFN = LIBTEMP: an existing library which will contain the members SIM7_DCLBISi, SIM7_USERINFOi, SIM7_DVCi and SIM7_OCL_TEMPp. These members are temporary and are for the internal use of the SIM7 step. For each simulation set, SIM7 builds these members and deletes them at normal end of the construction of the simulation set. NB: For debugging purposes, these members are not deleted in the case of an abort of the SIM7 program. 47 A2 83UR Rev00 5-7

32 Simulation of a TDS application with SIM7 (V5) User s Guide 5.4 The SIM7 job The job to activate the SIM7 step is in the member SIM7 of the SIM7.SLLIB. All its parameters and file assignments (refer to paragraphs 5.1 to 5.3) can be given values by means of keywords. Refer to the example at end of this paragraph. The following table shows for each parameter of the SIM7 step the associated keyword and the default value, if any, given by the SIM7 JCL. Parameter Keyword Default Mandatory parameters: TDSNAME &TDSNAME MASTER &MASTER TDSVERSC &TDSVERSC V6 TDSVERSS &TDSVERSS V7 SIMUSITE &SIMUSITE PROJOPER &PROJOPER OCLINTLS &OCLINTLS Y SETID1 &SETID1 SETMD1 &SETMD1 SETDVC1 &SETDVC1 Parameters dependant on the TDS application to simulate: SETIDn (2<=n<=36) &SETIDn (2<=n<=36) SETMDn (2<=n<=36) &SETMDn (2<=n<=36) &SETMD1 SETDVCn (2<=n<=36) &SETDVCn (2<=n<=36) &SETDVC1 Parameters dependant on the simulation site: SIMUV7TS &SIMUV7TS Optional parameters: MINTIME &MINTIME NIL MAXTIME &MAXTIME NIL MASTSIMU &MASTSIMU NIL LOADFACT &LOADFACT 1 File assignments used by the SIM7 step can be given values with the help of keywords A2 83UR Rev00

33 The builder phase Refer to the following table for the IFN name, the associated keyword and default value, if any, supplied by the JCL. IFN name Keyword Default USERJRNL USERJRNL LIBDECL LIBDECL SIM7.SLLIB LIBJCL LIBJCL &LIBDECL LIBTEMP LIBTEMP &LIBDECL EXAMPLE: If the SIM7 job is activated by the following command: EJR SIM7,,SIM7.SLLIB VALUES=(USERJRNL=TDS1.USERJRNL, LIBDECL=SIM7.SLLIB,LIBJCL=TDS1.JCL, TDSNAME=TDS1, MASTER=GCOS7, SIMUSITE=BCAA, PROJOPER=TILSOP,TDSVERSS=V7,SIMUV7TS=7458 SETID1=A, SETMD1=TSU001, SETDVC1=MS/B10, SETID2=B, SETMD2=TSU002); The name of the TDS to simulate will be "TDS1". The EFN of the sorted User Journal file will be TDS1.USERJRNL. The Master User name of the recorded session was "GCOS7". The Master User of the simulated TDS will be connected with name "GCOS7" under the "TILSOP" main project. The simulation will be executed on site "BCAA" running GCOS 7-V7 TS The set identifier of the first simulation set will be "A" (file SIM7.SCENA, member SIM7_DECLARATIONA, and so on). The file SIM7.SCENA will be preallocated on disk TSU001:MS/B10. If it is necessary (because of TILS internal table limits), SIM7 will automatically create a new simulation set identified by "B". In this case SIM7.SCENB is created on TSU002:MS/B10. The members SIM7_DECLARATIONA (and SIM7_DECLARATIONB if created), SIM7_CORRESPONDENTA (if any) and all SIM7 temporary members will be written to SIM7.SLLIB. The members SIM7_JCLA (and SIM7_JCLB if created), SIM7_OCLA and SIM7_CATA will be written to dynamically created library called TDS1.JCL. 47 A2 83UR Rev00 5-9

34 Simulation of a TDS application with SIM7 (V5) User s Guide The connection orders will be added at end of TILS_DECLARATIONA if only one set is necessary. Otherwise, the EXDIR statements for all connection orders will be automatically created in member TILS_OCLA of the library TDS1.JCL. 5.5 SIM7 Program errors Authorisation Checks The SIM7 program first checks to see if the SIM7 Marketing Identifier is installed. The following message is sent if it is not installed or no longer valid. SIM7 MI NOT INSTALLED OR SIM7 PROGRAM EXECUTION IS NO LONGER AUTHORIZED CONTACT THE SERVICE CENTER In such a case, the SIM7 MI must be installed or re-installed Errors in parameters The SIM7 program will check the validity of all the parameters before building the TILS scenario set(s). At each parameter error it encounters, it will send a message explaining the error. If at least one error is found in the parameters, the SIM7 program will be aborted. Appendix 2 gives a list of messages sent due to errors in parameters Unrecoverable errors during processing of the User Journal file Two cases of unrecoverable errors could occur. Those which provoke an abort of the SIM7 step and cause a message explaining the error to be sent to the user and written to the JOR. These messages are explained in Appendix 3 of this document. Others which provoke an abort of the SIM7 step and cause a message the following form to be sent to the Terminal user and written to the JOR: "FATAL : ERROR FROM SIM7 (REASON=XXX)" The main user errors which could provoke such aborts are given in Appendix 4 of this document A2 83UR Rev00

35 The builder phase For debugging purposes, when an unrecoverable error is found, the program aborts without any rollback either on library subfiles or on the scenario file Recoverable errors during processing of the User Journal file These errors correspond to a missing connection or disconnection record in the User Journal. If, for a given user, SIM7 finds that a connection or a disconnection record is missing, it sends a message to the Terminal User and to the JOR and continues processing as if the record were present. 5.6 End of the SIM7 Program The SIM7 step normally completes when no unrecoverable error is found and when all records of the input User Journal file have been processed. The following message is sent to the Terminal User and to the JOR at the normal end of construction of each scenario set: SIM > END OF CONSTRUCTION OF TILS SCENARIO SIM > FOR THE TDS: tdsname AND SET IDENTIFIER: i If SIM7 encounters at least one outward connection (e.g. a connection due to spawning), a message will be sent at the end of the SIM7 program indicating that the information contained in SIM7_CORRESPONDENTp of library LIBDECL must be included in the CRNETGEN (refer to paragraphs 0 and 0). 5.7 SIM7 Limits about 3980 input messages for one user (the messages of one user cannot belong to more than one simulation set). about 3980 input messages for one simulation set. But SIM7 treats user messages sequentially, as read from the sorted User Journal. So, if the number of input messages for one user is too high for the remaining space in the current simulation set, this set is closed, and another one is opened. SIM7 will discontinue filling up the first simulation set. about input messages for the whole simulation (see previous limit). 36 simulation sets for one TDS or for the total number of simulation sets on one site. 47 A2 83UR Rev

36 Simulation of a TDS application with SIM7 (V5) User s Guide 235 different users with outward connections in one simulation set connections for all the simulation sets. 500 abnormal disconnections for users with outward connections in one simulation set. 600 breaks for all the users of one simulation set. 255 different project/billing for all the users of one simulation set. 50 different userinfo messages at connection for all the users of one simulation set. maximum size of input message: 8200 bytes commands for the master user A2 83UR Rev00

37 6. The pre-simulation phase The SIM7 program is now normally completed ; all the simulation sets have been created. Some elements of these sets must be adapted to the site where the simulation is to take place. 6.1 Preparation of the TILS scenario set(s) Preparation of the SIM7_JCLi member(s) The JCL contained in the SIM7_JCLi member(s) built by SIM7 must be activated by means of an EJR. Check the $JOB card beforehand if the system is protected by access rights. In case of an abort of the TILS step, its output must be scanned to find the reason for the error. If it is due to the construction of the TILS Scenario contact your service center. If the connection orders are stored in a SIM7_DECLARATIONi member, and if after creation of the TILS command named SIMi the following messages appear: "** TRANSMISSION OF OCL STATEMENTS FAILED" with a return code SPACEOV from OPRTR "CORRECTIVE ACTION:"IGNORE","SKIP" OR "TERMINATE"" the following actions must be done: answer "TERMINATE" to the TILS question change OCLINTLS parameter value to N re-execute the SIM7 program 47 A2 83UR Rev00 6-1

38 Simulation of a TDS application with SIM7 (V5) User s Guide IMPORTANT: If several simulation sets are built by SIM7, check that all the SIM7_JCLi jobs can be run at the same time. A TILS step uses 5 to 6 MBytes of main memory on average. If the main memory of the system used for the simulation is not large enough, the machine can become overloaded before all the TILS steps can be activated. If such is the case, either the whole simulation may be impossible to run or its results cannot be analysed Checking of SIM7_DECLARATIONi and SIM7_CORRESPONDENTp If outward connections occurred during the collection phase of the TDS to be simulated, at least one SIM7_DECLARATIONi member will contain paths associated to a mailbox name: PATH username...mailbox=mbx-name (an outward connection corresponds for example to a connection made by the spawning mechanism). A 4 character mailbox name is created by SIM7. The local mailbox name of a terminal is recorded in its connection record as the 4 right-hand characters of the TERMINAL-ID field. SIM7 takes these four characters as the mailbox name for the user. These mailbox names created by SIM7 must not be the same as object names already known on the network. If one or more names already exist, the duplicate mailbox names must be manually changed in both the SIM7_DECLARATIONi and the SIM7_CORRESPONDENTp. 6.2 System preparation for the simulation phase Restoring the customer data files The user files, saved beforehand in the Collection Phase, must be restored. The external file names of these files must remain the same as on the customer site A2 83UR Rev00

39 The pre-simulation phase Checking the file options of the user files For the simulation phase, the user files are catalogued with the same sharing and journalisation options as on the customer system. LIST_FILE will allow the current file options to be obtained. Wrong options may be corrected by means of the MODIFY_FILE command. SHARE and JOURNAL values can be retrieved from a CATLIST of the customer SITE.CATALOG or private catalogs Modification of the SITE.CATALOG The SITE.CATALOG of the system where the simulation is to be replayed must be updated with the names of the users that are to be connected by TILS. They have the same names as the real-time users. The SIM7_CATp member, created in the LIBJCL library will contain CATMAINT commands to create PROJECTS, BILLINGS and USERS for all users that were recorded between MINTIME and MAXTIME in the User Journal of the collected TDS. This member must be updated with $JOB and $CATMAINT statements. The users with inward connections are connected under the same Projects and Billings that they had during the collection phase and retrieved from the User Journal. The TILS users are created and connected without any passwords. So, if some of the user names already exist in the SITE.CATALOG, they must be modified and have their passwords removed by the JCL command MDU project.username PASSWORD= ; The creation of a project is made by two CATMAINT statements: CRP and MDP. The "CRP project-name;" statement allows the project to be known to the CATALOG. If the project already exists, this statement is ignored. The "MDP project-name ADDAPPL=(tds-name/authority-codes);" statement will allow the TDS application to be linked to the project created by the previous CRP command or already existing in the SITE.CATALOG. Authority-codes are extracted from connection records of the TDS. The same sequence of CATMAINT commands (but only with the IOF application) is created for the MAIN OPERATOR project under which the TDS MASTER will be connected. 47 A2 83UR Rev00 6-3

40 Simulation of a TDS application with SIM7 (V5) User s Guide If for any reason, the connection record for a particular user is missing from the User Journal, the default value of "SIM7" is taken as both his project and billing for his connection during the simulation. If the master terminal was connected to IOF in the collected TDS, the project name under which the master operator must be connected for the purpose of the simulation is given by parameter PROJOPER. The master user name will be the same as that of the collected session unless a different value is specified for the MASTSIMU parameter of the SIM7 program in which case the master name will be the one given for MASTSIMU. The output produced by the job in the SIM7_CATp member must be checked for any errors or duplicate objects Preparation of the TDS Install the TDS on the simulation site using TP7PREP. The number of swap files and the size of each swap file must be the same as that on the original customer site Modification of CRNETGEN The SIM7_CORRESPONDENTp member will still exist in the LIBDECL at the end of the SIM7 program if outward connections occurred during the collection phase. It contains lines to be used by the CRNETGEN to create a configuration description directory. If a library member with a CRNETGEN configuration description directory already exists in the system, the lines containing "DIR" and "EDIR" must be deleted from the SIM7_CORRESPONDENTp member and the remaining lines inserted between "DIR" and "EDIR" of the CRNETGEN configuration description directory member. If there is no existing CRNETGEN configuration description directory member, then the SIM7_CORRESPONDENTp can be used as input to the "CRDIR" parameter of the CRNETGEN command. These modifications must be validated by the command: NGCRNET = NO CRDIR = member-name SAVE = SYSTEM ENABLE =1; A2 83UR Rev00

41 The pre-simulation phase Generation of the TDS After successful completion of the TDS preparation (cf ), the TDS must be generated. IMPORTANT: A TP7GEN is mandatory at each change of GCOS7 release or technical status Modification of the SITE.STARTUP Modification of the SITE.STARTUP is only required if the TDS master on the original customer site was connected to an IOF terminal. A startup must be created for the project associated with the master terminal operator (project supplied by PROJOPER parameter). This startup must include a MODIFY_PROFILE command to connect the terminal with the following parameters: PAGEMODE=0 NOVICE=0 MENU=0 GCLFORM=LINE Modification of the JCL containing the TDS step If the master terminal operator was not connected to a master mailbox in the TDS being simulated (MASTER ^= "MBXMBXMBXMBX" for SIM7 parameter), the statement "$CONSOLE MAIN;" must be inserted at the beginning of the TDS job. This statement allows the TILS simulation to use a special operator as master terminal. The name of this master is: either the one in the collected TDS (i.e. equal to the value of the MASTER parameter) if parameter MASTSIMU is not specified during call to SIM7. or the name associated to MASTSIMU parameter if it is specified. In both cases, the CRU and CRP of this user are part of the SIM7_CATp member. The TDS step of a simulation phase must start with the COLD option. To force it, the parameter OPTIONS= COLD must be added to the TDS step statement. 47 A2 83UR Rev00 6-5

42 Simulation of a TDS application with SIM7 (V5) User s Guide A2 83UR Rev00

43 7. The simulation phase 7.1 Activation of an SBR collect The SBR collect must be activated with all options (SNAPIC, SNAPMM, TDS, UFAS etc.). A further analysis of this file will allow you to compare the simulation with the behaviour of the application at the original site or the behaviour of the simulation in another environment (new release, new technical status, new versions of TPRs etc.). 7.2 Activation of the TDS job The TDS job, modified as explained in chapter is ready to be activated in COLD restart mode after the SBR command has been created. 7.3 ACTIVATION OF THE TILS SIMULATION The activation of the TILS step(s) simulating the complete TDS customer application is done by an EJR on all the SIM7_JCLi members. These steps can be launched in any order. The TILS steps are ready when the message "COMMAND SIMi CREATED" is received for each simulation set. These created SIMi commands allow the user to dialog with the TILS step: "ESC SIMi..." ; but, during a SIM7 simulation, it is recommended not to use these commands. In all cases, no SIMi command must be activated before the completion of the SIM7_OCLp job (refer to paragraph 7.4). 47 A2 83UR Rev00 7-1

44 Simulation of a TDS application with SIM7 (V5) User s Guide 7.4 Connection of TILS users Case where connection requests are in the SIM7_DECLARATIONi This is the simplest case but only occurs if the simulation of the complete TDS load requires only one simulation set and if the parameter "OCLINTLS" of SIM7 was equal to Y. The connection requests are supplied by the TILS step itself. No other user intervention is necessary Case where connection requests are in the SIM7_OCLp The TILS users are ready to be connected when all TDS and TILS steps are ready. All TILS connection requests are recorded in the TILS_OCLp member (with p equal to SETID1). The activation of this job allows the connection requests (immediate or deferred) to be given to the TILS steps for each user. The time of the first command of each simulation step will represent a time of origin for the whole simulation. So, in order to obtain good management of the time within the TILS simulation, no command must be executed manually before the completion of the TILS_OCLp job, and this member must not be modified. 7.5 The workload The connections, disconnections and all input messages of the TDS users are reexecuted under TILS. No special command is necessary during the whole period. 7.6 Stopping the simulation The TILS step(s) automatically stop after a duration equal to the difference of the MAXTIME and MINTIME parameters plus 10 minutes (the case where the parameter LOADFACT is equal to 1). If the TDS step is not terminated at this time (the case where no TTDS command is recorded in the User Journal), a TTDS command must be activated by a user of the OPERATOR project A2 83UR Rev00