Transporting Applications in Source Form › Using the Source Transport Utility › Setting Defaults › Running Traces

Running Traces

You can use the CA Ideal Trace Facility with the Source Transport Utility. Its use is affected by Source Transport's two‑phase processing. The @I$TRACE ON command turns on the trace. The SET @I$DIALMASK command specifies the Dial codes to show in a Dial trace. For more information, see the Problem Determination Guide.

• To turn on the trace before the processing of the commands in the source transport's first phase, put an @I$TRACE ON command before any source transport commands.
• To turn on the trace before the second phase, when the commands are processed, put the command just before the OFF.
• To turn off the trace after the first phase, put an @I$TRACE OFF command or an @I$TRACE PRINT command just before the OFF command.
• To trace the second phase, a second step in the job must print the trace because the @I$TRACE PRINT command must be processed after the OFF command in the first step is executed.

Invoking the User Exit

The Source Transport Utility provides exit points to facilitate the handling of exported CA Ideal source code by external library management systems. You can insert or verify control statements (or any 80‑column records) at these exit points.

The content of these added records does not affect an export or import. These records are placed before or after CA Ideal programs, panels, and reports on the external source file. You can use them for any purpose.

To activate these exit calls, enter one of the following commands anywhere in the command input stream:

SET EXIT LIBRARIAN
SET EXIT NAME load‑module‑name

SET EXIT LIBRARIAN

Calls the CA distributed load module @ISTEXIT. This module produces CA‑Librarian control statements. It is also distributed in source form as member STEXIT. It is provided as a sample and you can modify it. Refer to the appropriate installation guide for details on how to locate source members from CA distribution tapes.

SET EXIT NAME load‑module‑name

Specifies the site‑written exit called at the exit points. SET EXIT LIBRARIAN is equivalent to SET EXIT NAME @ISTEXIT. This exit must be linked Amode(31).

If you omit the command, no exit is called and no control statements are produced.

For the z/OS environment, the address of the JCL EXEC PARM= string is passed to the exit for its own use.

Export Exit

The export exit is called at the following times:

• First call of a run (for file headers)
• Beginning of each entity
• Ending of each entity
• Last call of a run (for file trailers)

Each is actually a series of calls under control of the exit, where each call can pass back an 80‑byte statement image that the Utility writes out to the external source file. Zero or more records can be written on the external file as determined by the exit.

The data passed to the exit lets the exit map the CA Ideal entity names into a user‑defined naming convention. This might be required when the same eight‑character name is used for programs in different systems or is used for related programs, panels, or reports. This mapping is the exit's responsibility.

The EXPORT exit can instruct the utility to do the following:

• Place a record on the external source code file and call again.
• Proceed to export the entity.
• Skip the current entity without exporting it.
• Abort the remainder of the processing.