To perform the operation on a Linux system, you need the side information file upicfile containing at least one entry with the name UPREPLAY. The entry must have the prefix SD or ND. For exceptions, see "Different platforms for Capture and Replay".
This entry must be a valid entry with the TAC of a service of the UTM application. (e.g. "DEMO"). The program UpicReplay uses this entry to address the UTM application. The program UpicReplay may set the TAC appropriately using data from the replay file.
Example of a upicfile entry
Replay with the TAC DEMO. The UTM application UTMTEST1 runs on the computer HOST5678.
SDUPREPLAY UTMTEST1.HOST5678 DEMO LISTENER-PORT=102 T-TSEL-Format=T
UTMTEST1 must have been generated either in MAX APPLINAME or in a BCAMAPPL statement.
Notes on UTM generation
During the UPIC Replay step, and in particular in the case of high load, the UTM application may need to permit more UPIC connections from the program UpicReplay than were originally present during recording. Consequently, it is advisable to use an adequately dimensioned UPIC terminal pool with multiconnect functionality for UPIC access, e.g.:
TPOOL LTERM=REPL,PTYPE=UPIC-R,CONNECT=MULTI,NUMBER=1000
In this case, up to 1000 UPIC clients can sign on simultaneously via the terminal pool.
If the UPIC Replay step runs at high load then it may be necessary to increase load-dependent generation parameters. In particular, you must pay attention to the following:
The UTM cache must be sufficiently large (MAX CACHESIZE)
The page pool must be sufficiently large (MAX PGPOOL)
The number of UTM tasks must be sufficient (MAX TASKS)
The number of permitted concurrent users must be sufficiently large (MAX CONN-USERS)
Different platforms for Capture and Replay
During replay, the data is transferred 1:1 to the UTM application. If the data includes, for example, hardware-dependent binary data, then this leads to errors if there is a change of platform. Consequently, the following applies:
It is not possible to record a UTM application session on BS2000 and then replay this with a UTM application on a Unix, Linux or Windows system. Reason: The data in the trace file is present in EBCDIC format and conversion to ASCII is not supported in UPIC.
It is not possible to switch between 32-bit and 64-bit platforms even within one and the same family of platforms.
It is possible to record a UTM application session on a Unix, Linux or Windows system and then subsequently play this back using a UTM application on a BS2000 system. One prerequisite is that only pure ASCII text data is transferred during the session.
In this case, you must enter HD as the prefix in the upicfile in order to ensure that the data is converted correctly between ASCII and EBCDIC.