The BPTD program uses a sub process to carry out the commands. If the number and type of commands issued do not cause this process to LOGOUT at the end then the sub process and the associated batch job will appear to hang in the batch queue. To see how far the process went review the output log file. Once in this state the sub process can usually be terminated using the STOP/ID command.
It is best to end the recorded commands with a LOGOUT. Then use the playback command to thoroughly test the commands to verify that the sub process terminates.
Every keystroke is recorded. All control characters are converted into strings of the form <<xxxxx>>. Any line breaks or returns that are introduced by editing this file will not cause any additional characters to be sent during playback.
Some menus may require a short pause before answering the menu prompt. Short pauses can be introduced by adding <<wait1sec>> at appropriate places in the recorded file. The number of seconds can be between 1 and 9. Use as many as needed to achieve the desired result. To determine if this is needed do the playback test with and without the delays, and check the results.
The DCL logout command when used inside a sub process causes that process to exit to the parent process. Inside a top level process it will cause that batch job to terminate immediately at that point. The standard post-amble that is added by EnterpriseSCHEDULE collects usage statistics from the job. The use of logout will skip these. To prevent this the schedule_login.com procedure redefines logout when inside a EnterpriseSCHEDULE job to allow these statistics to be gathered and proceeds with the exit.
