Table 1 System Commands cpy2view32—Generates Oracle Tuxedo VIEW32 definition file from COBOL copybook file.Specifies the output file name, followed parameter is the output file name. If this parameter is not specified, the output file name changes the suffix of the input file name to .v. For example, abc.cbl is converted to abc.v.* @binary: by default, copybook data types without the following qualifiers are converted to string: BINARY, COMP, COMP-1, COMP-2, COMP-3, COMP-4, COMP-5, PACKED-DECIMAL. With the * @binary=true annotation, the copybook data types without those qualifiers are converted to CARRAY. * @binary=false changes the conversion rule back to the default. When this annotation is defined on a group, all subordinates in the group are affected.The cpy2view32 utility is written in Java. You must install JDK 1.6 or above and add the Java command "java" to the PATH environment variable.
1.
3.
4. Listing 10‑1 through Listing 10‑4 provide Copybook and view file output examples:Listing 10‑1 Copybook Example 1Listing 10‑2 VIEW32 Output Example 1Listing 10‑3 Copybook Example 2Listing 10‑4 VIEW32 Output Example 2The following are general cpy2view32 limitations:
1. This tool does not parse REDEFINES clause, REDEFINES clause and their subordinate items are skipped.
2.
3. VALUE clause is skipped in the conversion.
4. SYNCHRONIZED clause is skipped in the conversion.
5. JUSTIFIED clause is skipped in the conversion.
6. Mif2View32—Generates VIEW32 definition file according to the metadata input file and updates the given FML32 definition file.Mif2View32 -i miffile -o viewfile -f fml32file -w webservice.desc [-v]Mif2View32 generates VIEW32 definition file according to the metadata input file and updates the given FML32 definition file. The generated nest VIEW32 definition file keeps the same structure with MIF; therefore, we can map the C structure to an FML32 structure.Mif2View32 supports the following options.-i miffile-o viewfile-f fml32file-w webservice.descSpecifies webservice.desc configuration file.
1. Listing 10‑5 provides an MIF example.Listing 10‑5 MIF Example
2. Listing 10‑6 provides a VIEW32 output file example.Listing 10‑6 VIEW32 Output Exampletcxcsdcvt -- translates RDO file to all z/OS resource configuration files.tcxcsdcvt translates RDO files to all z/OS resource configuration files.The generated resource configuration files by default are found in the current directory where this tool is run.tcxcsdcvt supports the following options:tcxmapgen — CICS Runtime MAPSET Generator.The generated physical (binary) file should be used in the MAPSET configuration file. See “Mapset Configuration File” in CICS Runtime Configuration Files.Specifies that only COBOL copybook (.cpy) output file is generated.Specifies a listing output file (.lst) is produced.Specifies that only binary mapset file (.mpdef) is produced.
Note: With -A, users can generate aligned map; without -A, users can generate unaligned map (default behavior).To compile the BMS source file file.map,use the following command:The resulting binary mapset file is file.mpdef.artadmin — ART CICS Runtime administration.The name of the profile file used for authentification. This parameter is useful for secure Oracle Tuxedoconfiguration. The profile file must be created with genappprofile. If no file name is provided, it defaults to ~/.ADMINappProfile.In some cases it is necessary to modify the configuration while the system is running. Normally, configuration changes which are relative to performances are managed by Oracle Tuxedo or the RDBMS level using commands (for example, tmadmin) or Oracle TSAM for Oracle Tuxedo dynamic configuration.artadmin is useful when making hot configuration changes in the CICS resources of a running ART CICS system. It allows the administrator to:artadmin is launched interactively (similar to tmadmin). When the artdmin is launched and connects to Oracle Tuxedo successfully, it returns a prompt requiring you to enter the commands.By default, the administration commands are transmitted to all servers in the ART CICS system. The configuration is global. For the newcopy, you may want to limit it to some specific servers. The sysid command is used to limit the command effect to the servers with a specific SYSID.
• The transactions.des TRANCLASS parameter cannot be changed dynamically.kixrpt.sh — ARTKIX transaction/command report utility.kixrpt reports transaction/command timing statistics information, including total number of transactions/commands running in specified time slot, total time cost, the average running time, etc. For each transaction/command, such tool reports the details of running information: total number, total time cost, average time cost, failure count, etc.kixrpt analyzes the standard output of ARTKIX servers to provide a summary of transaction / command processing time within the servers. The report shows the number of times dispatched and average elapsed time in milliseconds of each transaction / command in the covered period. kixrpt takes its input from the ARTKIX trace file or a directory (like KIX_TRACE_PATH) including trace files. The traces are valid by being set as below:KIX_TRACE_LEVEL=1 (or higher level)kixrpt supports the following options:
1. Set following environment variables before ARTKIX system is started:
2. After running some time, the statistic tool, kixrpt.sh, can be used to generate the report with given time slot.
3. Listing 10‑7 provides the output example:Listing 10‑7 kixrpt Output ExampleThe CESN transaction uses MAPSET CSIGNON. The following MAPSET definition must be added to the MAPSET configuration file ${KIXCONFIG}/mapsets.desc if CESN transaction is required:Using this default MAPSET definition, CESN supports a maximum eight-character password. If the following MAPSET definition is added to the MAPSET configuration file, CESN allows a maximum 32-characters password.If two MAPSET definitions are both added to the MAPSET configuration file, the default MAPSET definition CSIGNON is used. CESN, in this case, allows a maximum eight-character password.The CESN transaction ignores the UCTRAN setting in the TYPETERM configuration file. The username and password entered from terminal are always case-sensitive, no matter which UCTRAN value is set.