Version Language English. Product Menu Topics. Install DB2 Support.
|Published (Last):||15 January 2019|
|PDF File Size:||15.91 Mb|
|ePub File Size:||18.22 Mb|
|Price:||Free* [*Free Regsitration Required]|
Version Language English. Product Menu Topics. Install DB2 Support. Follow these steps:. The DBA must grant bind and execute authority to the plan created in the previous step.
For DB2 subsystems running in new function mode release This exit then collects DB2-related call information for every DB2 call done in the system. This can have significant performance implications in some DB2 shops. We recommend that you carefully review this prior to using the default settings. Specify the name of the load library which contains the demo programs:.
Modify the JCL according to the instructions in these members. CICS Level. If you believe there is an error in any of the entries, contact CA Technical Support. Complete the following steps to create your own symbolic file members:. This job does not require a link-edit step because it only updates the symbolic file.
No load module is produced. These commands are executed consecutively in the order of their appearance in the macros when either of the following commands is submitted:.
Where tablname. The command must be enclosed in apostrophes. Where nn. It must. These examples are shown for illustration purposes only. These commands are executed in sequence just as if they were entered manually from a terminal. Responses to them are written in the terminal's output sequential file. To reduce the amount of time required to process large numbers of CNTL commands, perform the following steps:.
Replace the CNTL commands in the sequential input with the following command:. Where name. Calls to Software and User Macro Support. For example:. In both cases, optional routines can be coded to do the following:. Check the parameters before the global routine is given control. If it does not, the user-written routine is mandatory. How Support Is Provided. The next section explains how to code these macros.
The macros create a table that, in addition to identification names and other information, contains references to the same routines that get link-edited with application programs because of CALLs issued by application programs.
These references are resolved at link-edit time. The IN25UEXI module consists of the table and the same modules that are usually link-edited with application programs. They are there only to compare a piece of their code with the code in the application load module. The compared pieces of code are at the offset from the entry point and the length specified in the IN25UEX macros. If a large piece of code is involved, there is no need to include all of it with the IN25UEXI; include just enough to make the comparison.
Monitoring resumes only upon return from the called module to the CALL statement. If there is a user-defined routine, the routine is performed first.
The routine can check the CALL's parameters and decide whether a particular interface should be given control or an automatic breakpoint should occur if the CALL is incorrect , and whether monitoring should continue when the interface returns to the calling program.
The entry points are specified by using one of the following formats:. This required parameter specifies the name of an entry point. Multiple entry point names can be specified, as shown in the second format; however, the optional parameters listed next cannot be used. This optional parameter specifies the name of your special routine.
Omit this parameter if there is no routine. This optional parameter specifies the length in decimal of the comparison. The maximum length is 64 and the default length is The default is sufficient in most cases.
This optional parameter specifies the offset in decimal from the entry point of the code to be compared. The maximum offset displacement is ; the default offset is 0. There is no need to include entire interface modules in the IN25UEXI, as the comparison occurs only for the specified or default length at the specified or default offset. Its source code is provided in the CAI.
Support Your Site's Global Routines. It applies to global routines that are given control by the following two machine instructions:.
This required parameter specifies a label that is defined in the CWA and contains the address of the entry point of a piece of commonly used code, such as a date conversion routine. For example, if the routine address is 20 bytes from the beginning of the CWA, you can code:.
Multiple entry point names can be specified as in the second format; however, if specified in this manner, the optional parameters listed next cannot be used.
CICS commands are not allowed. Registers 3 and 14 must not be changed by the routine. If these registers are used, they must be saved and restored by the routine. The application program registers 0 to 15 prior to the execution of the branch instruction are at 96 X'60' bytes past the address in register 3.
Monitoring must not continue if the code that is called by the monitored program does not return control to the next byte after the BALR instruction. Before the routine returns to the address in register 14, it must set register 0 to one of the following values:.
X'D0' X'FF'. The routine does not return control to the next byte after the BALR; therefore monitoring must be dropped. Any other negative value. To install this module, perform the following steps:. Calls for CA Gen Users. DB2 Support. DB2 Application Program Support. The installation procedure is explained next. Using the Pregenerated Version.
If you have programs that issue calls, or require special handling, review the section Calls to Software and User Macro Support. Modify this example to meet your system requirements.
To install this module, you must perform the following steps:. Monitor DB2 Applications. If you do not have any other special software situations that will be handled by the IN25UEXI program, you need not perform any additional installation steps for DB2 support. However, if you have programs that issue calls or require special handling, see Calls to Software and User Macro Support. This feature lets users view, alter, add, or delete data in DB2 tables without.
Handle Wild Branches. Such direct passing of control, although not advised by CICS coding standards, is used frequently in some applications. You cannot monitor just the program receiving control by a direct branch from another program. To monitor a receiving program, you must also monitor the program passing control to it. Monitoring can begin only with the program that originally received control from CICS.
Most often, the program receives control by a direct branch caused either by a CALL statement or by a special macro.
Monitor a Wild Branch. The receiving program resides in the same load module as the program that passes control. This facility lets you debug a subprogram as if it were a separate program and supports all language combinations. The receiving program resides in another load module that has a CICS program definition. Simply set breakpoints in the dynamically called program as you would for any other CICS program.
The receiving program resides elsewhere and has no CICS program definition. This allows online options to be used in the most convenient way, with different options such as breakpoints declared for different programs. Symbolic information for the default program must be saved in the symbolic file, and its name must be referenced in the FSYMP installation option.
This section explains how to define your own CORE keywords. User-defined CORE keywords provide a shorthand method for entering a complex CORE command by specifying a simple command that contains one or more of your own keywords.
16.20 - INTERTEST - IBM CICS Interface for Teradata
CA INTERTEST For CICS – Useful Commands
CA InterTest for CICS V10: Testing and Debugging 200