Restricting Script Datasets (VTAM)
Select option 3 Generate 3270 unattended statements using a standard script profile on the Generate 3270 Unattended Statements menu to apply generation restrictions. The following screen appears.
Generation Restrictions screen--------------------------- Generation Restrictions ---------------------------
Command ===>
Pre-process scripts - run these scripts prior to each of
the scripts selected below.
Restrict the generation of unattended statements to
script names beginning with the prefix, and/or scripts
for a particular application.
Script selection options:
Generate statements for scripts prefixed by . . . .
Generate statements for scripts for application . .
Post-process scripts - run these script after each of the
scripts selected above.
Press the ENTER key to continue, the END key to terminateUse this screen as described in Building-Unattended-Statements-and-JCL-VTAM. When you press Enter without entering a command, Performance Test validates the screen entries, generates unattended statements in the defined data set member, and refreshes the Generation Restrictions screen.
Use the Generation Restrictions screen to narrow the number of scripts for which Performance Test generates unattended statements. If you enter a prefix in unattended statement generation, Performance Test includes only script member names that begin with the prefix characters. If you enter an application in unattended statement generation, Performance Test includes only script members with that domain destination.You can also define scripts, such as logon and logoff scripts, to be run before and/or after the generated statements.
To run a series of scripts in sequence under one Group statement, use the options on this screen to generate the required statements. For example, to run SCRIPT1, SCRIPT2, and SCRIPT3 in sequence, enter SCRIPT1 as the preprocess script, SCRIPT2 as the script prefix, and SCRIPT3 as the postprocess script. The unattended statement generator then “sandwiches” SCRIPT2 between SCRIPT1 and SCRIPT3 and generates:
GROUP...
SCRIPT(SCRIPT1)
SCRIPT(SCRIPT2)
SCRIPT(SCRIPT3)When you press Enter without entering a command, Performance Test validates the screen entries, generates unattended statements in the data set member defined on the Unattended Statement Build screen, then shows that member on the ISPF EDIT screen.
ISPF EDIT Screen Showing Restricted Generated StatementsFile Edit Confirm Menu Utilities Compilers Test Help
-------------------------------------------------------------------------------
EDIT ACMJET0.UNATTND.CONTROL(CICSTEST) - 01.00 Columns 00001 00072
Command ===> Scroll ===> PAGE
****** ***************************** Top of Data ******************************
==MSG> -CAUTION- Profile is set to STATS ON. Statistics did not exist for
==MSG> this member, but will be generated if data is saved.
000001 CONTROL -
000002 BIND(1500) -
000003 KEYU(4500) -
000004 KEY2(2500) -
000005 PREFIX(EHPR) -
000006 SUFFIX(4) -
000007 SWAIT(25) -
000008 USDATE(YES)
000009 GROUP CICSTEST -
000010 LOGD(3) -
000011 REPEAT(1) -
000012 TERM(1) -
000013 THOPT(1)
000014 SCRIPT(LOGON)
000015 SCRIPT(EOB00046) -
000016 REPEAT(1)
000017 SCRIPT(LOGOFF)- After you make any desired edits, enter END to advance to the Unattended JCL Build screen. Refer to Building JCL for information on creating JCL to run your generated unattended statements.