Performance Test for VTAM Profile Defaults (VTAM)
Domain Traveler profile defaults
Domain Traveler provides an interactive connection from ISPF to the application or subsystem you are testing. Use it to record your activity, play back recorded scripts, compare recorded scripts to live activity, and dub new testing scripts.
Select option 1 Domain Traveler from the Edit Profile screen.
Edit Profile screen. --------------------------------- Edit Profile -------------------------------- .
. Command ===> .
. More: + .
. Primary commands: menu-number, ALL, CANCEL .
. Line commands: S or / to select options. .
. .
. Active Profile: .
. Dataset ===> 'PMIJSS0.JMS.ATV.PROFILE' .
. Member ===> PROFILE .
. Description ===> COPY FOR THE JAKEATV .
. .
. 1 Domain Traveler Recording and Playback defaults .
. 2 APPC Global Record and Script Create settings .
. 3 3270/LU0 Global Record and Script Create settings .
. 4 WebSphere MQ Global Record and Script Create settings .
. 5 TCP/IP Global Record and Script Create settings .
. 6 Playback MQ MQ Playback parameter defaults .
. 7 Playback TCP TCP Playback parameter defaults .
. 8 ATV Manager Test Vehicle defaults .
. .
. Should changes made elsewhere to Profile values be saved? .
. Profile Autosave ===> Y (Y = YES, N = NO OR A = ASK) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .The Domain Traveler Defaults screen appears.
Domain Traveler Defaults - session options and PF key translations
. -------------------------- Domain Traveler Defaults -------------------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: + .
. Default Domain ===> A13TSO (Recording Domain) .
. .
. Session Options .
. Logon Data ===> .
. ZOOM Mode ===> N (Y=Yes, N=No) .
. ZOOM Key ===> F23 .
. LU Name ===> (Terminal name used to login to application) .
. Logmode ===> SNX32705 (Overrides model, SNA and Queriable options) .
. 3270 Model ===> 5 (1=12x40, 2=24x80, 3=32x80, 4=43x80, 5=27x132) .
. SNA ===> Y (Y=Yes, N=No) .
. Queriable ===> Y (Y=Yes, N=No) .
. Trailing Blanks ===> 1 (1 = Single, Y = Keep all, N = Keep none) .
. Infirst ===> Y (Y = No Welcome Screen From Domain Dest.) .
. DBCS ===> N (Y = support DBCS) .
. Edit Application .
. Profiling ===> (/ to edit Application Profiling) .
. .
. The following PF key translations apply to the Domain Destination when .
. in non-Zoom mode: .
. PF01 = F1 PF04 = F4 PF07 = F7 PF10 = F10 PA1 = .
. PF02 = F2 PF05 = F5 PF08 = F8 PF11 = F11 PA2 = .
. PF03 = F3 PF06 = F6 PF09 = F9 PF12 = F12 CLEAR= .- Default Domain allows you to stay within ISPF and access Domain Destinations such as CICS, IMS/DC regions, etc. under which your business applications are run. Enter the desired default domain.
- The Domain Traveler Session Options are fairly straightforward. Fill in or change the desired fields.
- Logon data, if entered, will be supplied to the Domain Destination with your connection request.
- ZOOM mode. In non-Zoom mode, ISPF fills all fields with trailing blanks. Enter Y to initiate session in ZOOM mode and save all trailing blanks, N to initiate session in ISPF mode and remove all trailing blanks, or 1 to remove all but one trailing blank.
- ZOOM key specifies the key that will toggle between ZOOM and ISPF modes.
- LU name is the LU (terminal name) used when establishing a session with the application.
- Logmode describes the characteristics of the terminal (for example, rows and columns) when establishing a session with the Domain Destination. This entry must be defined to VTAM.
- 3270 model describes the type of 3270 device.
- SNA specifies whether Performance Test is emulating an SNA device.
- Queriable specifies whether Performance Test is emulating a queriable device.
- Trailing Blanks specifies whether Performance Test will save or remove trailing blanks. Y will keep all trailing blanks, N will remove all trailing blanks, and 1 will keep one trailing blank.
- Infirst specifies whether to provide a welcome screen from the domain destination. Y prevents the welcome screen from appearing.
- DBCS. Select Y to support double-byte character sets.
- Edit Application Profiling. Enter a (/) to view or modify your Edit Application Profiling settings. Application Profiling examines components of each datastream received from the application and compares it against previously received datastreams to better anticipate the next action the application will take (for example, to send more data or wait for input).
The default PF key translations apply to the Domain Destination when in non-Zoom mode. Make changes if desired.
PF01 = F1 PF04 = F4 PF07 = F7 PF10 = F10 PA1 =
PF02 = F2 PF05 = F5 PF08 = F8 PF11 = F11 PA2 =
PF03 = F3 PF06 = F6 PF09 = F9 PF12 = F12 CLEAR=
Remainder of Domain Traveler defaults. -------------------------- Domain Traveler Defaults -------------------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: - + .
. PF03 = F3 PF06 = F6 PF09 = F9 PF12 = F12 CLEAR= .
. .
. Recording Parameters: .
. Script Dataset ===> 'VP.CMU.QQF172.INSTALL3' .
. Replace Members? ===> Y (Y=Yes, N=No) .
. Format Recording ===> Y (Y=Yes, N=No) .
. Record Inputs .
. Only? ===> N (Y=Yes, N=No) .
. Script Recovery ===> Y (Y=Yes, N=No) .
. Input Fields ===> N (in row,column format? Y or N) .
. .
. Playback Parameters: .
. Repetition Count ===> 1 (1 to 999) .
. Zoom Mode ===> N (Y)es, (N)o, (R)esume .
. Dubbing ===> N (Y)es, (N)o, (C)hange only .
. Suppress Play .
. Screens ===> N (Y=Yes, N=No) .
. Stop Play ===> (Y=Yes, N=No) .
. Play/Think Time ===> 1 ( 1. Play interactively, .
. 2. Play at full speed, .
. 3. Play at think time recorded on script, .
. 4. Play at user specified think time) .
. Identify inputs whose processing should be delayed: .
. ===> .
. Think Time .
. Seconds ===> 01 (If Play/Think Time .
. Hundredths ===> 50 option 4 selected) .
. Percentage ===> 100 (If Play/Think Time is 3 or 4) .
. .
. Comparison Options ===> 4 (1. Any compare check .
. 2. Alpha character differences .
. 3. Field number mis-matches .
. 4. Ignore all compare differences) .
. .
. Initial Mismatch ===> DELTA (ACTUAL,DIFFER, or DELTA) .
. .
. Ignore Numeric .
. Differences ===> N (Y=Yes, N=No) .
. Compare Last .
. Image Only ===> N (Y=Yes, N=No) .
. Dub Encrypted Masks .
. as Character .
. Masks ===> Y (Y=Yes, N=No) .
. Use Encrypted .
. Masks During .
. Compare ===> N (Y=Yes, N=No) .
. Identify outputs whose compare processing should be bypassed: .
. ===> .
. .
. Auto Documentation Parameters: .
. Dataset Name ===> 'PMIJSS0.HIPER.VTAM.AUTODOC' .
. File Format ===> 1 (1 = Printer Control Characters .
. 2 = DCF (Script) Tags .
. 3 = None) .
. Record ===> 3 (1 = Output screens .
. 2 = Input data with output .
. 3 = Both) .
. Screens "boxed" ===> Y (Y=Yes, N=No) .
. Running Title ===> Jake's sample autodoc .
. .
. Other Datasets: .
. Journal Dataset ===> 'PMIJSS0.HIPER.VTAM.JOURNAL(JOUR0001)' .
. Log Dataset ===> HIPERLOG.LIST .- Fill in or change the Recording Parameters fields.
- Script dataset specifies where you want to store created scripts on DASD. This must be a fully qualified data set name up to 44 characters and defined as a PDS or PDSE. If the data set does not exist, you will be prompted to allocate it.
- Replace Members? Enter Y to replace existing scripts with dubbed scripts.
- Format Recording specifies whether to create a formatted script. Enter a Y to create a formatted script.
- Record Inputs Only? Enter a Y to record only the input entries. If selected, screen images will not be recorded. Enter an N to also record screen images.
- Script Recovery specifies whether to use script recovery. Enter a Y to use script recovery.
- Input fields specifies whether to record the physical row and column of the input rather than the relative input number. Enter a Y to record the physical row and column.
- Fill in or change the Playback Parameters fields.
- Repetition Count specifies the number of times to repeat. Enter 1 to 999.
- Zoom Mode specifies whether the script will play in zoom or non-zoom mode. Enter Y for zoom mode, N for non-zoom mode, and R to play the script in zoom mode, but return to non-zoom mode when the script is finished.
- Dubbing allows you to record a new script during the play process.
- Enter Y to invoke the Standard Recording Setup screen. This activates the normal recording mode. The status line will change to indicate that recording is active.
or - Enter C to invoke the change-only Recording Setup screen during execution setup. This activates a background recording that is only saved if the original script encounters a comparison check. The status line is not changed.
- Enter Y to invoke the Standard Recording Setup screen. This activates the normal recording mode. The status line will change to indicate that recording is active.
- Suppress Play Screens:
- Enter Y to invoke the standard Recording Setup screen. This will activate the normal recording mode. The status line will change to indicate that recording is active.
- Enter C to invoke the change-only Recording Setup screen. This will activate a background recording that will only be saved if the original script encounters a comparison check. The status line is not changed.
- Stop Play: Enter Y to halt activity during playback.
- Play/Think Time specifies the think time to be used during playback. The options include:
- Play interactively: Playback pauses before each screen of data is sent to the Domain Destination.
- Play at full speed: Transactions are played back as fast as the system can execute them.
- Play at Think Time recorded on script: Think time is simulated using the time recorded on the script.
- Play at user specified think time: Think time for all transactions will be the time specified in the “Time (ss th)=>” field.
- Identify inputs whose processing should be delayed: Enter a range of <INPUT> groups whose playback should be delayed. Use this option when the application takes an unusually long time to build the screen into which the <INPUT> group is placed. Only use this field if prior playbacks failed because Performance Test processed these particular <INPUT> groups too quickly.
- Think Time (when option 4 is selected): The Think Time for each transaction specified in seconds, tenths, and hundredths of a second. For example, “00 75" specifies 3/4 of a second think time.
- Percentage applies a percentage figure to the Think Time. This option is applicable when the Play/Think Time is set to 3 or 4. For example to play back a script with half the original think time, enter Play/Think Time ===> 3 and Percentage ===> 50.
- Fill in or change the Comparison Options fields.
- The Stop/Mark Comparison Option (COPT) specifies an unattended comparison option that is effective only when used in conjunction with the LOG or XLOG parameters. Choices include:
- Any compare check: Mark all comparison checks in the log.
- Alpha character differences: Mark only alpha character differences. Ignore differences in screen attribute bytes.
- Field number mismatches: Mark comparison checks only if there is a difference in the number of fields on the received and expected screens.
- Ignore all compare differences: Ignore all comparison checks.
- Initial mismatch specifies which screen is to be placed when a mismatch is detected.
- ACTUAL$: The ACTUAL screen displays the contents of the buffer that Performance Test received from the application.
- DELTA $: The DELTA screen displays an overlay of the position that is different from the actual screen versus the expected screen.
- DIFFER$: The DIFFER screen displays an overlay of the differences between the actual screen versus the expected screen. This overlay is on top on the ACTUAL screen.
Ignore numeric differences (IGND) specifies that numeric values will not be considered when testing for comparison checks. The IGND keyword is only in effect when used in conjunction with the LOG or XLOG parameters. Performance Test considers the following conditions as matching:
- Actual character and expected character are both numeric.
- Actual character is numeric and the expected character is blank or null.
- Actual character is blank or null and the expected character is numeric.
All other conditions are mismatches.
- Compare last image only compares the scripted screen image and the screen image received from the application only after the application has sent all data required to build the final screen. For example, many applications send a map filled with data followed by a map containing only a message. Enter a slash (/) in this field to eliminate comparison of the first data only map but to allow comparison when the full screen image is built from both the data and the message maps.
- Dub encrypted masks as character masks dubs encrypted masks (<MSK>NNN tags) in the script being played back to the new script as both encrypted masks and as an additional record of “I” character masks when you select Y. Select N to prevent additional character masks from being added to your dubbed script.
- Use encrypted masks during compare to prevent miscompares on dark fields. Deselect this option to disable encrypted masks and allow identification of miscompares within dark fields. Deselecting this option does not cause data within dark fields to appear on Actual/Expected screens. This option affects only encrypted masks. All other forms of masking are still valid and in effect for dark fields.
- Identify inputs whose compare processing should be bypassed bypasses compare processing for <OUTPUT> groups that fall within the specified range. For example, enter 1-3,6,77 to bypass compare processing for <OUTPUT> groups 0000001, 0000002, 0000003, 0000006, and 0000077.
- The Stop/Mark Comparison Option (COPT) specifies an unattended comparison option that is effective only when used in conjunction with the LOG or XLOG parameters. Choices include:
- Fill in or change the Auto Documentation Parameters fields.
- Dataset name specifies whether the output generated by the AutoDoc facility is directed to a SYSOUT class or DASD data set. If you enter a single character, the documentation produced by the AutoDoc feature is allocated to a SYSOUT class. If you enter more than one character, the documentation is allocated to a data set file.
- File Format specifies the AutoDoc format that will be generated in standard print formatting and carriage control (PCC), Document Composition Facility script (DCF), or neither of these formats. Enter 1 (PCC), 2 (DCF), or 3 (NONE).Record can produce AutoDoc documentation for the output images, screen images with the entered input, or both. Enter 1 (output screens), 2 (input data with output), or 3 (both).
- Screens “boxed” produces documentation with or without borders. Enter Y to produce documentation with borders or N for no borders.
- Running Title specifies the title that will appear at the top of each page. You can use up to 57 characters.
- Fill in or change the Other Datasets fields.
- Journal Dataset specifies that a transaction journal will be generated for the 3270 group. If the specified value is a single character, the journal is allocated to a SYSOUT class. The SYSOUT goes to the class specified by that character. If the value is more than one character, the transaction journal is allocated to a permanent file with that data set name. By default, no transaction journal report is produced.
- Log Dataset specifies that a comparison log for each terminal in the group will be allocated. If the specified value is a single character, the comparison log is allocated to a SYSOUT data set. The SYSOUT data set is in the class specified by that character. If the value is more than one character, the comparison log is allocated to a permanent file with the name dataset.P nnnn where nnnn is the port number assigned to the terminal. Wildcards (* or ?) can be used for the port number (nnnn). A member can also be supplied.
3270/LU0 Profile Defaults
The 3270/LU0 - Record and Script Create Defaults screen specifies the Terminal LU, Applid, and/or UserID you want to record.
Select option 3 3270/LU0 from the Edit Profile screen. The 3270/LU0 Record and Script Create Defaults screen appears.
Edit Profile screen. --------------------------------- Edit Profile -------------------------------- .
. Command ===> .
. More: + .
. Primary commands: menu-number, ALL, CANCEL .
. Line commands: S or / to select options. .
. .
. Active Profile: .
. Dataset ===> 'PMIJSS0.JMS.ATV.PROFILE' .
. Member ===> PROFILE .
. Description ===> COPY FOR THE JAKEATV .
. .
. 1 Domain Traveler Recording and Playback defaults .
. 2 APPC Global Record and Script Create settings .
. 3 3270/LU0 Global Record and Script Create settings .
. 4 WebSphere MQ Global Record and Script Create settings .
. 5 TCP/IP Global Record and Script Create settings .
. 6 Playback MQ MQ Playback parameter defaults .
. 7 Playback TCP TCP Playback parameter defaults .
. 8 ATV Manager Test Vehicle defaults .
. .
. Should changes made elsewhere to Profile values be saved? .
. Profile Autosave ===> Y (Y = YES, N = NO OR A = ASK) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .3270/LU0 Record and Script Create Defaults screen
. ------------------ 3270/LU0 Record and Script Create Defaults ----------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: + .
. --------------------------------Record Settings-------------------------------- .
. Message Filters ("/" for Filter panel) .
. .
. Capture Criteria: .
. Terminal ===> * Use an asterisk for wildcarding .
. Application ===> * the Terminal, Application or Userid .
. User ID ===> * fields. .
. OR .
. Global Record Manager List ===> select to edit list .
. Second Filter GRM List ===> select to edit list .
. .
. Start and End Times: .
. Date and Time HH : MM : SS MM / DD / YY .
. Start Time ===> 00 : 00 : 00 Start Date 00 / 00 / 00 .
. End Time ===> 00 : 00 : 00 End Date 00 / 00 / 00 .
. .
. Repository Dataset: .
. Dataset Name ===> 'PMIJSS0.EXAMPLE.REPOS*' .
. First Number ===> 1 (if wildcard in dataset) .
. Last Number ===> 5 (if wildcard in dataset) .
. Replace or Append ===> 1 (1 = Replace, 2 = Append) .
. .
. Recording Options: (Enter "/" to select) .
. Suspend Script Creation .
. / Re-use Repositories .
. FORCE Request at 'End Time' .
. / Normal Event Notification .
. / Error Event Notification .
. Record From LOGON Only .
. .
. -----------------------------Script Create Settings---------------------------- .
. Script Dataset: .
. Dataset Name ===> 'PMIJSS0.JMS.SCRIPTS' .
. Description ===> SMOKE TEST VTAM DEC2022 .
. Member Prefix ===> DEC22 (1 - 6 character prefix) .
. Member Suffix ===> (2 - 7 numeric suffix) .
. Session Log ===> (1 - 8 character member name) .
. Replace? ===> (/ = Yes, Blank = No) .
. .
. Script Format Options: (Enter "/" to select) .
. / Format the Recording Blank to generate unformatted .
. Input Only Blank to capture input and output .
. / Input Field Formats Change Input Fields to Row/Column Format .
. .
. Message Filtering Options: (Enter "/" to select) .
. Use Message Filters (Use REXX Scripts) .
. I Filter Default (I = Include, E = Exclude) .
. .
. Script Create Execution Options: .
. Select Processing Option: (Enter number to select) .
. 1 1. Submit Batch Job .
. 2. TSO .- Entering a slash (/) to select Message Filters displays the 3270/LU0 - Message Filters screen. See the applicable sections in this space or the online help for information about creating these filters.
The Capture Criteria fields specify what you want to capture. Fill in the Terminal, Application, and/or User ID fields or the Global Record Manager List field.
- Terminal specifies the logical unit (LU) name of the VTAM terminal to record.
- Application specifies the ID of the VTAM application to record.
- User ID specifies the mainframe User ID to capture.
For Terminal and Application, you can enter a fully-qualified 8-character name. For User IDs you can enter a fully-qualified 7-character name. You can also use a wildcard (*) to capture all terminals, Applids, and User IDs—or you can specify a group of terminals, Applids, and User IDs starting with the same prefix (for example, TEST*).
If you prefer, you can specify a Global Record Manager List and, optionally, a Second filter GRM List instead of the Terminal, Application, and User ID fields. These fields can only be specified if the Terminal, Application, and User ID fields are left blank.- Global Record Manager List and Second Filter GRM List specify the name of a Global Record Manager INCLUDE or EXCLUDE list. If you specify a list that does not exist, when the user reaches this point in the record process, the Global Record Manager * Add List screen will appear to allow the user to create the list before the capture criteria is accepted. To use the Second Filter GRM List, you must first have specified the Global Record Manager List. The second filter will be applied to the result of the first filter.
- Start and End Date and Time are optional fields that specify the date and time of day that you want the capture request to be started or stopped. If you enter a Start Time you must enter a Start Date. If you enter an End Time you must enter an End Date.
- Repository Dataset specifies the name of the data set where captured data will be stored on DASD. You can enter a fully-qualified data set name up to 44 characters in this field to allocate a fixed repository. You can also enter a data set name with a wildcard of “*” or “?” that will result in the allocation of a repository set. This set is defined by a range of numbers entered in the First and Last number fields.
Enter the data set name and First Number and Last Number fields, if required.- Asterisk (*): Inserts an incremented value into the data set name qualifier in which the asterisk appears. This wildcard pads the incremented value with enough zeros to ensure an eight-character qualifier. For example, USER.#3270.REC* with first=1 and last=3 creates capture the following repositories:
USER.#3270.REC00001
USER.#3270.REC00002
USER.#3270.REC00003 Question mark (?): Inserts the incremented value into the data set name qualifier where the question marks appear. Enter at least one question mark for each digit of the greatest value in the range fields. For example, USER.#3270.REC?? with first=9 and last=11 creates the following capture repositories:
USER.#3270.REC09
USER.#3270.REC10
USER.#3270.REC11- First Number and Last Number define the range for wildcard characters entered in the Repository Dataset field. You can enter any range from 0 to 9999999. These fields are required only if you enter a wildcard in the repository data set name.
- Replace or Append specifies whether the captured data will be appended to a data set of the same name or replace it. Enter 1 to replace or 2 to append.
- Asterisk (*): Inserts an incremented value into the data set name qualifier in which the asterisk appears. This wildcard pads the incremented value with enough zeros to ensure an eight-character qualifier. For example, USER.#3270.REC* with first=1 and last=3 creates capture the following repositories:
- Recording Options control the way your capture request will generate scripts, process the repository, stop your requests, send normal and/or error messages, and capture in-flight session data.
Enter a slash (/) to select an option.- Suspend Script Creation controls automatic script creation. To prevent script creation at the end of the recording request, enter a slash (/) in this field and press Enter. It also defers the entry of script creation criteria to a later time. If you leave this field blank you will be guided through the script creation criteria screens prior to your capture request being activated. This will also cause automatic script creation to execute when your capture request is stopped.
- Re-use Repositories controls whether repository sets will be reused when the last data set in the sequence is filled. Enter a slash (/) to reuse your repository sets. For example, if you enter a First and Last number of 0000001 through 0000010, when segment number 10 is full, the data recorder will close segment 10 and reopen segment 1 replacing the oldest captured activity with the newest. Leave this field blank to terminate recording when the last segment is full.
- FORCE Request at 'End Time' controls whether your capture request will be forced rather than stopped when it reaches the End Time you specified in your request. FORCE terminates recording of all sessions including in-flight sessions. Script creation begins immediately unless the Suspend script creation option is selected. Be aware that you may lose buffered data, resulting in partially recorded sessions.
If you do not select this option, a STOP command is issued at the request’s specified end time. It stops recording new sessions, but continues to record any active sessions. After all in-flight sessions end, recording terminates and script creation begins unless the Suspend script creation option is selected. Although this ensures complete session captures, it may delay script creation.
This field can only be selected if you entered an End Time in your request.
Enter a slash (/) to select. - Normal Event Notification and Error Event Notification control whether normal and error event messages are generated and sent to your TSO session. If you are recording a large number of sessions, consider disabling Normal event notification to reduce the number of messages you receive.
Enter a slash (/) to receive these messages at your terminal or leave blank to disable sending messages. - Record From LOGON Only controls whether to start capturing sessions that are already in flight when the request is started. If you leave this field blank, your capture request will start capturing data for sessions that have already been logged on and meet your capture filter criteria. If you enter a slash (/), your request will only capture sessions that log on after the request is started.
- Specify the Script Create Settings.
- Script Dataset Name, Member Prefix, and Member Suffix specify the fully-qualified data set and member names where you want to store your scripts. Enter a 1-6 character prefix and/or a 2-7 numeric suffix. Enter a Description if desired.
- Session Log specifies the name of the log file for this session. Enter a 1-8 character member name.
- Replace? specifies whether the script data set will replace a data set of the same name. A slash (/) = yes and blank = no.
- Specify the Script Format Options.
- Generate Formatted Script specifies whether formatted or unformatted scripts will be generated. Enter a slash (/) to generate formatted scripts or leave blank to generate unformatted scripts.
- Input Only specifies whether to capture input only or input and output. Enter a slash (/) to capture input only or leave blank to capture input and output.
- Input Field Formats allows you to change input fields to a row/column format. Enter a slash (/) to select.
- Specify the Message Filtering Options. Message Filtering lets you filter the data in your 3270 or LU0 sessions so that only the inputs and outputs you are interested in are stored in the script. You typically use Message Filtering to limit the size of your scripts and to create scripts containing only specific messages or transactions. You write short programs in REXX to tell Performance Test the parts of a session to keep and parts to ignore. REXX programs that you write can examine the screen images and user input that flow during a session. You then set indicators in your REXX programs to identify the screen images and user input Performance Test should keep or ignore. Enter a slash (/) to select.
- Use Message Filters controls the formatting of your scripts. Enter a slash (/) to apply message filters to your captured data during script creation. Leave blank, and message filters will not be used during script creation even if you specified them in the 3270/LU0 - Message Filters screen.
- Filter Default. Enter I to include or E to Exclude.
- Script Create Execution Options specifies whether you want background (batch) or foreground processing to be your default. Sample JCL is provided for a batch job, which you can change if desired. Select one of the following:
- 1 Submit Batch Job (background). If you select this option, you must specify a valid OS JCL jobcard in the Job statement information for batch job field.
- 2 TSO (foreground). This option will execute script creation as a foreground task under your TSO session. Your session will remain locked until script creation processing completes.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*