Date Change and Date Find Script Processors (VTAM)
The Date Change and Date Find script processors search through Performance Test for VTAM scripts and find or change date fields.
Date change script Processor
The date change script processor allows you to move dates forward in baseline Performance Test scripts. The date change script processor finds date input and output fields (such as a delivery date) in recorded scripts, then transforms the year portion of the date from a two-digit to a four-digit number.
For example, if a recorded delivery date field is <I01>"05/30/07", the date change script processor automatically changes it to <I01>"05/30/2007". The change is stored in a new output script created by the script processor.
Select option 2 Date Change on the Script Processors screen to use the Date Change Script Processor.
Script Processors Menu. ----------------------------- Script Processors ------------------------------- .
. Option ===> .
. .
. .
. 1 REXX Processor Create "Smart" Script(s) .
. 2 Date Change Change Year Formats for Date Testing .
. 3 Date Find Report Location(s) of Date Field(s) .
. 4 Input Field Formats Change Input Fields to Row/Column Format .
. 5 MultiChange Processor Update Scripts to Reflect Application Changes .
. 6 Security Script Processor Locate and Modify Passwords .
. 7 Euro Euro Script Utility .
. 8 GST GST Testing Utility .
. 9 Message Filtering Message Filtering Utility .
. .The following screen appears:
Script Processor * Date Change Options screen. -------------------- Script Processor * Date Change Options ------------------- .
. Option ===> .
. .
. .
. 1 Single Field Dates Dates with separators .
. 2 Multi-Field Dates Month, Day and Year contained in .
. separate fields .
. 3 Embedded Dates Manipulation of Month, Day and Year .
. Fields separately .
. .
. Userid . PMIJSS0 Date . . 23/03/01 Time . . 13:43 .
. .
. .
. .
. .
. Enter END command to return to Script Processor Menu. .- Select one of the following date change options:
- 1 Single Field Dates — converts year values to four-digit format as described in Single Field Dates.
- 2 Multi-Field Dates — converts year values to four-digit format for dates split into more than one field as described in Multi-Field Dates.
- 3 Embedded Dates — replaces the data for a date as described in Embedded Dates.
- Press END to exit the date change script processor and return to the Script Processors menu.
Single Field Dates
Select option 1 Single Field Dates to use the Single Field Date Script Processor. The following screen appears:
Single Field Date Change screen. --------------------------- Single Field Date Change -------------------------- .
. Command ===> .
. .
. Go Begin Date Change Execution .
. END Return to Script Processor Primary Option Panel .
. .
. Identify the Screen to process: .
. Screen ID . . . . * .
. ID Location . . . ** , *** (Row,Col) .
. .
. Describe Input Dates to Change: .
. Date Separator Character. / (Enter N for no date separator) .
. Date Format . . . . . . . 1 (1-8 or * for all formats) .
. .
. Describe Output Dates to Change: .
. Date Separator Character. / (Enter N for no date separator) .
. Date Format . . . . . . . 1 (1-7) .
. Date Location . . . . . . ** , *** (Row,Col) .
. Allow ATR overlay . . . . Y (Y/N) .
. .
. Valid Date Formats are: .
. 1. MMDDYY 3. YYMMDD 5. DDMONYY 7. MMYY .
. 2. DDMMYY 4. YYDDD 6. YYMON 8. YY .Use this screen to change two-digit years to four-digit format for dates stored in single fields.
- Identify the screen to process by entering the Screen ID for the screen where the multi-field date is input or shown. This field is case sensitive — the uppercase and lowercase characters must match the screen ID in the script exactly. If the text does not match exactly, the script processor will not recognize the screens that require synchronization processing. Wildcards are not allowed. The wildcard character is treated as the actual screen ID.
- Enter the ID Location (screen row and column location) of the screen ID text. Valid row numbers are between 1 and 43. Valid column numbers are between 1 and 132. Enter ** (asterisks) as wildcards in the row field and *** in the column field to indicate that the screen ID text can be found anywhere on the screen.
If a row and column are entered into the screen ID location fields, the row and column must be the screen row and column position where the text starts. Do not make any adjustments to account for attribute bytes. For example, if the screen ID is located in the upper left corner of the screen, the position of that text may not be row 1, column 1. There may be an attribute character in position (1,1) with the text beginning at (1,2). In this case, specify 1,2 for the screen ID location fields.
If the screen ID is an * (asterisk), the ID location must be **,***. If the screen ID location is incorrect, the script processor will not recognize the screens to be processed, and no script processing will occur for this entry. - Fill in the Describe Input Dates to Change and/or Output Dates to Change to change only input fields, only output fields, or both input and output fields.
- Input Date Separator Character — divides the month, day, and year of the date. For example, for a date of 06/01/07, the date separator character is a slash (/). Enter an asterisk (*) to indicate that the date separator character can vary. Enter N to indicate that no date separator character is used in the date fields.
Input Date Format — describes the arrangement of the day, month, and year date components. Valid values are 1 through 8, or an asterisk (*). Enter an asterisk (*) to have the script processor handle all eight date formats.
- Output Date Separator Character — divides the month, day, and year of the date. For example, for a date of 06/01/07, the date separator character is a slash (/). Wildcards are not allowed in this field.
- Output Date Format — describes the arrangement of the day, month, and year date components. Valid values are 1 through 7. Wildcards are not allowed in this field.
- Date Location — specifies the row and column location of the date on the output screen. Row numbers must be between 1 and 43, and column numbers must be between 1 and 132. To process dates appearing anywhere on the screen, enter ** for row number and *** for column number.
- Allow ATR overlay — specifies whether to overlay the screen area with the expanded year if it contains attribute bytes. Enter Y to indicate that the screen area can be overlaid irrespective of its content. Enter N to reject the request when the screen area contains attribute bytes.
- Type Go and press Enter to begin date change execution or END to exit the date change script processor and return to the Script Processor * Date Change Options screen.
- When you press Enter, the Script Processor Execution screen appears. This screen allows you to enter the data sets used in script processing as described in Running the Date Change Script Processor.
Multi-Field Dates
To use the Multi-Field Date Script Processor, select option 2 Multi-Field Dates. The following screen appears:
Multi-Field Date Change screen. --------------------------- Multi-Field Date Change --------------------------- .
. Command ===> .
. .
. Go Begin Date Change Execution .
. RESet Initialize input fields .
. END Return to Date Change Options Panel .
. .
. Identify the Screen to process: .
. Screen ID . . . . * .
. ID Location . . . ** , *** (Row,Col) .
. .
. Enter Input Date Change Information: .
. Month . . . . . . Input field number or Location row,col .
. Day . . . . . . . Input field number or Location row,col .
. Year. . . . . . . Input field number or Location row,col .
. .
. Enter Output Date Change Information: .
. Month . . . . . . , (Row,Col) .
. Day . . . . . . . , (Row,Col) .
. Year. . . . . . . , (Row,Col) .
. Allow ATR overlay (Y-Yes, N-No) .You can use this screen to change dates contained in multiple input fields on an application screen from two-digit years to four-digit years.
- Enter the Screen ID where the multi-field date is input or shown. This field is case sensitive — the uppercase and lowercase characters must match the screen ID in the script exactly. If the text does not match exactly, the script processor will not recognize the screens that require synchronization processing. Wildcards are not allowed. The wildcard character is treated as the actual screen ID.
- Enter the ID Location (screen row and column location) of the screen ID text. Valid row numbers are between 1 and 43. Valid column numbers are between 1 and 132. Enter ** (asterisks) as wildcards in the row field and *** in the column field to indicate that the screen ID text can be found anywhere on the screen.
If a row and column are entered into the screen ID location fields, the row and column must be the screen row and column position where the text starts. Do not make any adjustments to account for attribute bytes. For example, if the screen ID is located in the upper left corner of the screen, the position of that text may not be row 1, column 1. There may be an attribute character in position (1,1) with the text beginning at (1,2). In this case, specify 1,2 for the screen ID location fields.
If the screen ID is an * (asterisk), the ID location must be **,***. If the screen ID location is incorrect, the script processor will not recognize the screens to be processed, and no script processing will occur for this entry. - For the input and output Month, Year, and optionally Day, specify a field number between 1 and 999 OR its position on the screen (row number between 1 and 43 and column number between 1 and 132, separated by a comma).
Performance Test scripts mark input fields with the eye catcher <Ixx>, where xx is the number of the input when specifying a field number and <I(rr,ccc)>, where rr,ccc is the row and column number when specifying a row,column format. Enter either the relative input numbers or the row and column numbers (when the script locates Input by row and column position) of the year, month, and optionally the day. - Specify whether to Allow ATR overlay. Y indicates that the screen area can be overlaid with the expanded year irrespective of its content even if it contains attribute bytes (not recommended). N indicates that the request should be rejected when the screen area contains attribute bytes (recommended).
- Issue one of the primary commands to continue:
- GO begins the date change script processor. When you press Enter, the Script Processor Execution screen appears. This screen allows you to enter the data sets used in script processing as described in Running the Date Change Script Processor.
- RESET changes all values on this screen to blanks.
- END exits the date change script processor and returns to the Script Processor * Date Change Options screen.
Embedded Dates
To use the Embedded Date Script Processor, select option 3 Embedded Dates. The following screen appears:
Embedded Dates Change screen. ---------------------------- Embedded Dates Change ---------------------------- .
. Command ===> .
. .
. Go Begin Date Change Execution .
. RESet Initialize input fields .
. END Return to Date Change Options Panel .
. .
. Identify the Screen to process: .
. .
. Screen ID . . . . * .
. ID Location . . . ** , *** (Row,Col) .
. .
. Enter date change information: .
. .
. Date Field .
. Input number or Location of Month Day Year .
. Position in Input Field of. Month Day Year .
. For a Length of . . . . . . Month Day Year .
. Change To . . . . . . . . . Month Day Year .
. Move To Position. . . . . . Month Day Year .Use this screen to process the Month, Day, and Year as separate integers embedded within a single input field. This function is only available for input dates.
- Enter the Screen ID whose input dates are to be changed. This field is case sensitive — the uppercase and lowercase characters must match the screen ID in the script exactly. If the text does not match exactly, the script processor will not recognize the screens that require synchronization processing. Enter an asterisk (*) to process all screens.
Enter the ID Location (screen row and column location) of the screen ID text. Valid row numbers are between 1 and 43. Valid column numbers are between 1 and 132. Enter ** (asterisks) as wildcards in the row field and *** in the column field to indicate that the screen ID text can be found anywhere on the screen.
- In the Input number or location of field, specify the number of the input field in which the value is contained. In the script, input fields are designated by <Inn> or <I(rr,ccc)> where nn is the input number and rr,ccc are the row and column positions. For example, if the script had <I01>"Dec", <I06>"25", and <I11>"2006", enter 1 in the Month row, 6 in the Day row, and/or 11 in the Year row. In the Input Number column, you must enter a value in each row for which you want to replace data. This field is required.
- Specify the Position in Input Field. This is the relative position of the data within the input field. For example, if the script had <I01>"ACME 25DEC2006" enter 8 in the Month row, 6 in the Day row, and/or 11 in the Year row. You do not need to enter a value in this column if the corresponding month, day, or year data begins in the first position of the input field. This field is optional.
- In the For a Length Of field, specify the length of the data to be replaced. For example, if the script had <I01>"ACME 25DEC2006" enter 3 in the Month row, 2 in the Day row, and/or 4 in the Year row. This field is mandatory only when the Position field is greater than 1.
- In the Change To field, specify the value that will replace the existing data. Entries are checked for valid day, month, or year values. In the Change To column, you must enter a value in each row for which you want to replace data.
- Specify the Move to Position. This is the relative position of the replacement data within the input field. Normally, this column is used only if the length of the Month, Day, or Year data is being changed in the For a Length Of column.
- Issue one of the primary commands to continue:
- GO begins the date change script processor. When you press Enter, the Script Processor Execution screen appears. This screen allows you to enter the data sets used in script processing as described in Running the Date Change Script Processor.
- RESET changes all values on this screen to blanks.
- END exits the date change script processor and returns to the Script Processor * Date Change Options screen.
Running the Date Change Script Processor
After entering date change requirements on one of the Script Processor * Date Change screens, type GO on the command line and press Enter to continue. The Script Processor * Execution screen appears.
Enter the name of the Script Partitioned Data set. ------------------------- Script Processor * Execution ------------------------ .
. Command ===> .
. .
. blank Continue .
. .
. Type the names of the script data sets below, then press Enter key .
. Do not specify the script/member name .
. .
. Input Script Data Set: .
. Project . . . .
. Group . . . . .
. Type . . . . .
. .
. Other Partitioned Data Set: .
. Data Set Name . . . 'PMIJSS0.HIPER.VTAM.SCRIPTS' .
. .
. Output Script Data Set: .
. Project . . . .
. Group . . . . .
. Type . . . . .
. Other Partitioned Data Set: .
. Data Set Name . . . 'PMIJSS0.HIPER.VTAM.SCRIPTS.OUTPUT' .Enter the name of the data set (not including the member) that contains the recorded scripts to be processed and the name of the data set (not including the member) to use for storing the processed scripts and press Enter. The Script Processor * Execution screen appears.
List Script Names for processing. ------------------------- Script Processor * Execution ------------------------ .
. Option ===> .
. .
. F Initiate Processing In Foreground. .
. B Initiate Processing In Background. .
. .
. Input Script Data Set: 'PMIJSS0.HIPER.VTAM.SCRIPTS' .
. Output Script Data Set: 'PMIJSS0.HIPER.VTAM.SCRIPTS.OUTPUT' .
. .
. INPUT SCRIPT NAME OUTPUT SCRIPT NAME .
. SAMP0000 SAMP0000 .The input and output script data sets are prefilled from the previous screen and cannot be changed.
- Type the names of the recorded input scripts to be processed and the names of the corresponding new output scripts to be created by the script processor.
- The input scripts are members of the data set listed in the Input Script Data Set field. Enter an asterisk (*) in this field to process all members in the data set.
- The output scripts are members of the data set listed in the Output Script Data Set field. There must be an output script name for every input script name. The same script can be both the input script and the output script. In this case, the script processor will overwrite the original script. If you enter an asterisk (*) for the input script name, you must also use an asterisk for the output script name.
- Specify whether to Replace Existing Members. If an output script already exists, this field determines whether to overwrite it. Enter Y to overwrite existing scripts.
- Type F or B on the Option line. F initiates the script processor in TSO foreground. B allows the script processor to run in the background (batch). Background mode frees your terminal while the script processor runs.
Date Find Script Processor
The Date Find Script Processor is designed to assist testing applications where dates are important. The date find script processor searches through the output screens of recorded Performance Test scripts and finds date fields. The date fields that it finds are listed in a report. The following figure shows a sample Date Find Location Report.
Sample Date Find Script Processor Report
**********************************************************************
****** HIPERSTATION SCRIPT PROCESSOR DATE FIELD LOCATION REPORT ******
**********************************************************************
SCRIPT NAME: ’CWX0001.HIPERPRO.SCRIPTS(DATECH)’
DATE FORMAT: 1 DATE SEPARATOR: /
SCRIPT MESSAGE NUMBER DATE LOCATION (ROW,COL) DATE FOUND
----------------------------------------------------------------------
1. <OUTPUT>0000001 (05,30) 08/28/07
2. ** SAME ** (13,39) 8/22/07
3. ** SAME ** (15,60) 5/13/07
4. <OUTPUT>0000005 (01,01) 09/25/07
5. ** SAME ** (23,12) 08/28/07
6. <OUTPUT>0000007 (01,01) 01/01/07
7. ** SAME ** (23,12) 08/28/07
**********************************************************************
****** HIPERSTATION SCRIPT PROCESSOR DATE FIELD LOCATION REPORT ******
**********************************************************************
SCRIPT NAME: ’CWX0001.HIPERPRO.SCRIPTS(DATECH2)’
DATE FORMAT: 1 DATE SEPARATOR: /
SCRIPT MESSAGE NUMBER DATE LOCATION (ROW,COL) DATE FOUND
----------------------------------------------------------------------
1. <OUTPUT>0000001 (05,30) 08/28/07
2. ** SAME ** (13,39) 8/22/07
****** HIPERSTATION SCRIPT PROCESSOR DATE FIELD LOCATION REPORT ******
**********************************************************************
SCRIPT NAME: ’CWX0001.HIPERPRO.SCRIPTS(DATECH)’
DATE FORMAT: 1 DATE SEPARATOR: /
SCRIPT MESSAGE NUMBER DATE LOCATION (ROW,COL) DATE FOUND
----------------------------------------------------------------------
1. <OUTPUT>0000001 (05,30) 08/28/07
2. ** SAME ** (13,39) 8/22/07
3. ** SAME ** (15,60) 5/13/07
4. <OUTPUT>0000005 (01,01) 09/25/07
5. ** SAME ** (23,12) 08/28/07
6. <OUTPUT>0000007 (01,01) 01/01/07
7. ** SAME ** (23,12) 08/28/07
**********************************************************************
****** HIPERSTATION SCRIPT PROCESSOR DATE FIELD LOCATION REPORT ******
**********************************************************************
SCRIPT NAME: ’CWX0001.HIPERPRO.SCRIPTS(DATECH2)’
DATE FORMAT: 1 DATE SEPARATOR: /
SCRIPT MESSAGE NUMBER DATE LOCATION (ROW,COL) DATE FOUND
----------------------------------------------------------------------
1. <OUTPUT>0000001 (05,30) 08/28/07
2. ** SAME ** (13,39) 8/22/07
Using the Date Find Script Processor
Select option 3 Date Find on the Script Processor menu. The following screen appears:
Script Processor * Date Find screen
. ------------------------- Script Processor * Date Find ------------------------ .
. Command ===> .
. .
. Go Begin Date Find Execution .
. END Return to Script Processor Primary Option Panel .
. .
. Enter date find information: .
. Date Separator Character. . / (Enter N for no date separator) .
. Date Format . . . . . . . . 1 (1-14) .
. 1. MMDDYY 5. MMDDYYYY 9. DDMONYY 13. YYYYMON .
. 2. DDMMYY 6. DDMMYYYY 10. DDMONYYYY 14. MMYYYY .
. 3. YYMMDD 7. YYYYMMDD 11. YYMON .
. 4. YYDDD 8. YYYYDDD 12. MMYY .
. .
. Specify the date find report file name: .
. .
. Project . . . .
. Group . . . . .
. Type . . . . .
. Member. . . . .
. Other Data Set Name: .
. Data Set Name . . . 'PMIJSS0.JMS.SCRIPTS(DATERPT)' .- Specify the Date Separator Character. This character divides the month, day, and year of the date. For example, for a date of 05/01/07, the date separator character is a slash (/). The date separator is required when the date format is 1 through 8. If the date format is 9 through 14, the script processor automatically determines the date separator character (if there one). Enter N to indicate that no date separator character is used in the date fields.
- Select a Date Format to describe the arrangement of the day, month, and year date parts. Valid date formats are 1 through 14 (see the Script Processor * Date Find screen).
- Specify the date find report file name. This is the name of the data set used to store the Date Find Location Report. If the file does not exist, you are prompted to provide one with a data set allocation screen. The data set must be a data set member or a sequential file. The recommended record format is fixed block with 80-byte record length.
- Issue one of the primary commands to continue:
- GO begins running the scripts through the date find script processor.
- END exits the date find script processor and returns to the Script Processors menu.
Running the Date Find Script Processor
After entering the date separator, the date format, and the report file name on the Script Processor * Date Find screen, type GO on the command line and press Enter to continue. The Script Processor * Execution screen appears.
Enter the name of the Script Partitioned Data set file
. ------------------------- Script Processor * Execution ------------------------ .
. Command ===> .
. .
. blank Continue .
. .
. Type the name of the script data set below, then press Enter key .
. Do not specify the script/member name .
. .
. Input Script Data Set: .
. Project . . . .
. Group . . . . .
. Type . . . . .
. .
. Other Partitioned Data Set: .
. Data Set Name . . . 'PMIJSS0.HIPER.VTAM.SCRIPTS' .Enter the name of the data set (not including the member/script names) containing the recorded scripts to be processed and press Enter. The Script Processor * Execution screen appears.
List script names For processing. ------------------------- Script Processor * Execution ------------------------ .
. Option ===> .
. .
. F Initiate Processing In Foreground. .
. B Initiate Processing In Background. .
. .
. Input Script Data Set: 'PMIJSS0.HIPER.VTAM.SCRIPTS' .
. Report File Data Set : 'PMIJSS0.JMS.SCRIPTS(DATERPT)' .
. .
. INPUT SCRIPT NAME .
. SAMP0000 .The Input Script Data Set and Report File Data Set fields are prefilled and cannot be changed on this screen. The Report File Dataset is the file where the Date Find Location Report will be stored.
- Enter the name of the recorded scripts to be processed in the Input Script Name field. The scripts are members of the data set listed in the Input Script Data Set field. Enter an asterisk (*) as the script name to process all members in the data set.
- To begin processing, type F or B on the Option line and press Enter. F Initiates the script processor in TSO foreground. B allows the script processor to run in the background (batch). Background processing frees your terminal while the script processor runs.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*