Previous Topic

Next Topic

Book Contents

Book Index

Common edit changes made to 'keystrokes' captured scripts

Once a script is recorded and imported into EnterpriseSCHEDULE it is common to make edit changes. Recorded responses can be changed into Job parameters and/or Schedule variables including date variables. The dynamic token substitution can be added to the session, for example:

You could use a Job parameter such as parameter 1

$ write sys$output "((P1))"

You could use a Schedule variable

$ write sys$output "((endofmonth))"

where endofmonth is a variable in the same directory as the job.

For previewing the outcome that the commands will be after dynamic token substitution of variables and parameters.

$ schedule preprocess {jobname}

(Note: from the Schedule Windows Client use the "preview" commands button.)

If 'P1' was 'Hello world', then "preprocess" would return

$ write sys$output "Hello world"

In the GE Centricity menu example above you may want to make

"ECOMMERCE MEDICARE IDX 4010" a Job parameter such as "((p1))".

$ define sys$output NL:

$ CACHE -"UBIS"

S X=$ZU(68,5,0) S SECID="BISPROD",BYPASS=1 D ^%ZIDSEC H

XXX

BAR

1

99

61

1

10

((p1))

Y

N

See Also

Appendix H - Job Commands using 'keystroke' capture

General guidelines

Using Schedule Command line Client to capture an interactive session

Breaking 'keystrokes' Jobs into reusable pieces using include within a Job

Creating 'keystrokes' prototype Job Templates