bmc-ctd-dal-transformer-cli Utility

The bmc-ctd-dal-transformer utility transforms reports without using Control-D/WebAccess Server Web Application or the Control-D Mainframe. This process enables you to verify that the necessary files and resources are available for specific reports in offline mode. The bmc-ctd-dal-transformer transforms AFP, PCL, PDF, PostScript, and XEROX reports to the following file formats:

  • HTML

  • PDF

  • TXT

  • PCL

Running the bmc-ctd-dal-transformer-cli Utility

This procedure describes how to run the bmc-ctd-dal-transformer-cli utility, which enables you to batch transform reports.

Begin

  1. Log in to a host where Control-D/WebAccess Server is installed.

  2. Type the following command:

    bmc-ctd-dal-transformer-cli <-r=> <-p=> <-i=> <-t=> <-o=> <-y=> [-l=Log_Config_Path]

  3. For each field, define the required parameters, as described in bmc-ctd-dal-transformer-cli parameters.

  4. Continue with the on-screen instructions until the configuration is complete.

bmc-ctd-dal-transformer-cli parameters

The following table describes the bmc-ctd-dal-transformer-cli parameters.

Parameter

Description

-r: Root_Directory

Defines the root directory and must include the following sub-directories:

  • config: Contains the log.ini and the transformer.ini configuration files. Log.ini defines the location of the transformer log file (transformer.log). Transformer.ini defines transformer parameters.

  • cvt: Contains temporary resources to transformed them into an intermediate format.

  • input: Contains the available reports that require transformation.

  • log: Contains transformer log files.

  • output: Contains intermediate files and the output file.

  • res: Contains all the resources required for the transformation.

-p: Report_Name

Defines the section name, which states report parameters in the transformer.ini file, which is located in the root_directory \configdirectory, as described in Transformer.ini configuration file for further information.

-i: Input_File_Name

Defines the report filename to transform.

The specified file must be in the root_directory \input directory or type the full path to transform a file in a different location.

-t: Input_File_Type

Determines the input report file type to transform.

Valid values:

  • XRX

  • AFP

  • PCL

  • PS

-o: Output_File_Name

Defines the filename of the transformed report.

The specified file must be in the root_directory \output directory or type the full path to output a file to a different location.

-y: Output_File_Type

Determines the report output file type.

Valid values:

  • HTML

  • PCL

  • PDF

  • TXT

A TrueType font appears as text in the output file, other font types appear as an image, as discussed in Control-D/WebAccess Server Font Mapping.

-l: Log_Config_Path

Defines an alternate path to the log.ini file when the file is not in the root_directory \config directory, as described in, Log.ini configuration file.

Transformer.ini configuration file

The transformer.ini configuration file contains parameters to transform report formats.

The following example shows a sample transformer.ini file.

Copy 
Transformer.ini configuration file
[ Report_name ]
ReportCliqueName= report_name
XResolution=96
YResolution=96
Rotation=0

Replace [report_name] with the full report name or report mask, in brackets.

You can use the transformer.ini file to override report clique parameters, as described in Report Clique Parameters.

Log.ini configuration file

The log.ini file defines the types of log errors and their location.

The following example illustrates a log.ini file, which defines an error log and info log in the [transformer] section.

Copy 
[transformer]
channels=error_file,info_file
screen-level=error
[error_file]
type=text-file
path=../log/transformer-error.log
level=error
[info_file]
type=text-file
path=../log/transformer-info.log
level=info

The following example illustrates a log.ini file, which defines an error log in the [transformer] section.

Copy 
[transformer]
channels=error_file
screen-level=error

OverridingReportFormat

The OverridingReportFormat parameter enables you to transform Xerox LCDS and AFP Category 3 and 4 reports to HTML or PDF.

You can only define the OverridingReportFormat parameter in the transformer.ini file with the bmc-ctd-dal-transformer-cli utility.

A decollated text report, with the filename Hour appears as a regular text report. You must add the following parameters to the transformer.ini file when the report contains a section named Hour to view a report in PDF or HTML.

Copy 
[hour]
OveridingReportFormat=AFP
AfpInputType=AfpCategory4;
afpformdefname=F1xxxx;
AfpPAGEDEFName=P1xxxx;
AfpRecDelim=rdw;
RecordLength=133;
AfpPrintControlChar=ASA;
AfpInputCode=EBCDIC;
AfpInputTrc=No;

Transforming AFP reports

This procedure describes how to transform AFP reports using the bmc-ctd-dal-transformer-cli utility.

Begin

  1. Determine the report FORMDEF.

  2. In the transformers.ini file, add a section with the report name and define the FORMDEF, as described inTransformer.ini configuration file.

  3. Do one of the following:

    • Save the report in binary format in the root_directory\input directory.

    • Decollate the report and save it in your local file.

  4. Continue with step 6 when the report contains all resources.

  5. Download the resources as described in AFP Resources.

  6. Upload the resources to the root_directory\res directory.

  7. Delete the contents of the root_directory\cvt directory.

  8. Run the bmc-ctd-dal-transformer-cli utility, as described in bmc-ctd-dal-transformer-cli Utility.

  9. Verify that all resources are present by doing the following:

    1. Open the transformer-info.log file, as described in Transformer Problem Determinations.

    2. Check the log file for error messages.

      ERROR: BMCDAL0009E TCL.PrepareTransformObject: Missing resource C1H200D0 (Type: 7)

  10. Repeat Step 5 to 8 until all resources until there are no error messages in the transformer.log file).

Transforming Xerox reports

This procedure describes how to transform XEROX reports using the bmc-ctd-dal-transformer-cli utility.

Before you begin

Prepare a list with the following information:

  • Start JSL.

  • Start JDE.

  • All JSLs and JDEs.

Begin

  1. In the transformers.ini file, add a section with the report name, the start JSL, and start JDE as described inTransformer.ini configuration file.

  2. Decollate the report in Control-D Mainframe with print CDAM parameter ASSOC=XRX.

  3. Save the report in the Control-D/WebAccess Server root_directory\input directory.

    The report is now in rdw format even though the original report is fixed format.

  4. Add a command to the syscatlg.cat resource file in the root_directory \res directory when the JSL sees a missing JDE/PDE resource.

    SYSCAT TYPE=PDE,RESNAME=PP0010,FILE=PDE001,CRDATE=1997250.

    CRTIME=132200,SIZE=0,PATH='PDE001.JSL';

    In this example, the JDE/PDE name is PP0010, which appears in the PDE001.JSL file.

  5. Upload the resources to the root_directory\res directory.

  6. Delete the contents of the root_directory\cvt directory.

  7. Run the bmc-ctd-dal-transformer-cli utility, as described in bmc-ctd-dal-transformer-cli Utility.

  8. Verify that all resources, which present by doing the following:

    1. Open the transformer-info.log file, as described in Transformer Problem Determinations.

    2. Check the log file for error messages.

      ERROR: BMCDAL0009E TCL. Size: Missing resource IDF824 (Type: 12289)

  9. Repeat Step 5 to 8 until all resources until there are no error messages in the transformer.log file.

Transformer Problem Determinations

An error message appears in the log file when the transformation process fails. Error messages appear in the transformer-error.log or the transformer-info.log of the log.ini file. The default location is installation_directory\log.

A file does not transform when a critical resource is missing. g, A failure might occur when the FailOnMissingResources parameter is set to Always and a non-critical resource is missing.