Operations

The following Operations table lists the available operations.

Function	Environment	Name
Extract	Transaction Agent	XATZBOOK
Execute Batch	Transaction Agent	XACTCDLL
ListCopy	Transaction Agent	XATZCEXT
ListDir	Transaction Agent	XATZRDIR
JCL Generator	Transaction Agent	XATZCJCL
Functional Test Client Interpreter	Transaction Agent	XATZCXML
Virtualization	Batch	XATZMOCP
Execute CICS EXCI	Batch	XATZCICX
Compare	Batch	XATZCMPR
Handle CICSCALL	CICS	XATZCCEI
Execute CICS	CICS	XATZCCEX
CICS Plan Exit	CICS	XATZCDBP
CICS Command Processor Controller	CICS	XATZCCPR
CICS Command Processor	CICS	XATZCCPE
Interface to CICS Command Processor	CICS	XATZCCEZ
Virtualization	CICS	XATZMOCC
SQL Utility¹	XATZCCEX/XATZCDLL	XATZCSQL
Utility for XATZSGET²	XATZSGET	XATZSGER
Export data set	Batch	XATZWXML
Import data set	Batch	XATZWXRE
Verify data set	Batch	XATZDVER

^{1 Contained in XATZCCEX and XATZCDLL.}

^{2 Contained in XATZSGET.}

The zFS file system is used to temporary store input/output data for component executions and optionally collect code coverage information. Component execution data is normally deleted after each execution, but occasionally it might not be deleted.

Each user should have allocated about 10-50 MB space.

The space needed for code coverage collection depends on how many modules are being executed, how often they are executed and how large the modules are.

The Total Test server has a clean-up mechanism that will delete old files. It can be configured to after how many days files should be deleted, and this option also influences the requirements to storage size.

Operations

BMC AMI DevX Total Test

On this page