CA Spool. Java Transformers Administration Guide. Release 11.7

Transcription

1 CA Spool Java Transformers Administration Guide Release 11.7

2 This documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 CA Technologies Product References This document references the following CA Technologies products: CA Bundl CA Common Services CA Dispatch CA View Contact CA Technologies Contact CA Support For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback About Product Documentation If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is available on the CA Support website at

4

5 Contents Chapter 1: Introduction 11 Xenos d2e Vision Xenos d2e Vision Engine Xenos Field Technology Xenos Font Mapping Xenos Developer Studio Parsers AFP Parser Metacode Parser Generators PCL Generator PDF Generator PostScript Generator How the Java Transformers Work Features and Benefits Chapter 2: Installing the Java Transformers 21 Software Requirements CA Common Services Requirements How CA MSM Works Distribution Libraries Target Libraries Concurrent Releases Chapter 3: Installing Your Product from Pax-Enhanced ESD 27 How to Install a Product Using Pax-Enhanced ESD How the Pax-Enhanced ESD Download Works ESD Product Download Window USS Environment Setup Allocate and Mount a File System Copy the Product Pax Files into Your USS Directory Download Using Batch JCL Download Files to Mainframe through a PC Create a Product Directory from the Pax File Sample Job to Execute the Pax Command (Unpackage.txt) Copy Installation Files to z/os Data Sets Contents 5

6 Receiving the SMP/E Package How to Install Products Using Native SMP/E JCL Prepare the SMP/E Environment for Pax Installation Run the Installation Jobs for a Pax Installation Clean Up the USS Directory Apply Maintenance HOLDDATA Chapter 4: Starting Your Product 51 How to Complete Deployment With CA MSM Start CA Spool Java Transformers Step 1: Restore the Java Transformer TAR Backup Step 2: APF Authorize the CA Spool PDSE Library Step 3: Add the Java Transformer JCL Procedure Step 4: Configure the Java Transformer Environment Variables Step 5: Update the CA Spool Initialization Parameters Step 6: Enter the LMP Code Step 7: Verify the Installation Chapter 5: Customizing the Transformers 65 Initialization Parameter Statements DEFNODE NODE X2YY X2YYDEF System Configuration File Parameters JobVariables LocalizedMessageFile DefaultReportPath ReportManager LogMessageOptions InputMonitor JobManager LicenseAuthentication ResourceManager ComponentDefinition TuningOverride IoCache Transformer Parameter Files Sample Master Font Correlation Tables Java Transformers Administration Guide

7 Sample Transformer Parameter Files Default Master Font Correlation Tables Default Transformer Parameter Files Common Transformer Parameters Filedeflist FileDef iohandlerfactoryinstance Tuning MFCT Common Parser Parameters Common Generator Parameters AFP Parser Parameters Parameters FileDef DefaultPageSize ResGroupOption PrinterOptions ResourcePreview SkipInlineResOptions LineDataExtraction ImagePassThroughOptions MediumMapOptions ExternalResources CommentRecordingOptions BcocaOptions Metacode Parser Parameters Parameters FileDef StockDefinition PreloadJSLList MetacodeOriginTable ResourcePreview CommentRecordingOptions DmgTagProcessing LineDataMethod PCL Generator Parameters FileDef ShiftBy Image Options ShadeMap DefineFeed PDF Generator Parameters Contents 7

8 Parameters FileDef AcrobatOpen Compress ShiftBy ElementPlacementPrecision Encryption Linearization PostScript Generator Parameters FileDef DefineFeed ShadeMap ShiftBy XIF Parameters XifFragmentJoining XifLineJoining XifShadeJoining XifVectorOptions XifDrawingOptions XifRasterOptions XifTextOptions Chapter 6: Using the Master Font Correlation Table 161 The Master Font Correlation Table Edit the MFCT Rules for Editing the MFCT <afpcharsetmapping> AFP Charset Input Fonts Table Parameters <afpcolortable> AFP Color Table Parameters <afpfamilymapping> AFP Typeface Input Fonts Table Parameters <afpgengocacolortable> AFP GOCA Output Color/Pattern Map Table Parameters <afpglyphtable> AFP Glyph Table Parameters <codepageicutable> ICU Table Parameters <colortable> Color Table Parameters <metacolortable> Metacode Color Table Java Transformers Administration Guide

9 Parameters <metafamilymapping> Metacode Input Fonts Table Parameters <metafontmapping> Metacode Input Font Mapping Table Parameters <opentypefontmappings> AFP OpenType Input Fonts Table Parameters <outputfont> Output Fonts Table Parameters <translationtable> Translation Table Parameters PCL Typeface Values Table Appendix A: Messages 187 Return Codes CA Spool ESFLOG Messages Java Transformer Server D2ELOG Messages Java Transformer Subtask D2ELOG Messages Index 205 Contents 9

10

11 Chapter 1: Introduction This section presents an overview of the CA Spool Java Transformers which provides AFP and Metacode data stream conversion support. This is done by integrating with Actuate s Xenos d2e Vision which is written fully in Java, so zaap processors can be utilized. These new CA Spool Java Transformers allow automatic conversion of AFP and Metacode/DJDE/LCDS documents into PCL, PostScript, and PDF documents. The new CA Spool Java Transformers will be utilized by all CA ERM products to transform documents into specific data-stream formats before storing and for ad-hoc data-stream transformation. For example, converting Metacode documents into PDF on the fly for online viewing. This section contains the following topics: Xenos d2e Vision (see page 11) Parsers (see page 13) Generators (see page 15) How the Java Transformers Work (see page 17) Features and Benefits (see page 19) Xenos d2e Vision The Xenos d2e Vision base product includes all of the following functions and components: Xenos d2e Vision Engine The Xenos d2e Vision engine controls how all components operate, and runs jobs in batch, lights-out, or on-the-fly modes. Staying active between jobs, the engine maintains a resource cache for improved performance. Highly scalable and written 100% in Java, the Xenos d2e Vision engine requires Java Virtual Machine (JVM) 1.5.x or higher. Chapter 1: Introduction 11

12 Xenos d2e Vision Xenos Field Technology Xenos Field Technology (XFT) is a flexible, document-oriented method of extracting any content from a document using rules to define page sections and fields. With the Xenos Field Technology (XFT) Component of Xenos d2e Vision, you can define fields, then review, edit, and use the fields to make the most of the data in your print stream. XFT uses the Xenos Intermediate Format (XIF), which contains all of the objects within a page parsed by a parser. The text elements in XFT are normalized to Unicode, allowing support for double-byte character sets (DBCS) and Cyrillic or other non-iso-latin-1 character sets (also known as Acrobat s Win ANSI encoding). Threshold rules control how these characters are joined into words, words into phrases, and phrases into paragraphs. Xenos Font Mapping Xenos Font Mapping provides options for mapping or rendering incoming document fonts from print streams into the desired output formats. These options include: Making a raster image of each word, which provides a high-quality rendition where no equivalent output font exists. Font mapping with control over each character's translation where each word (defined by blank delimited or non-printable characters) is placed precisely as it must be. The PDF Generator also supports mapping into embedded Type 1 fonts. A combination of raster images and font mapping where most characters of the font are mapped to an outgoing font but some special characters are turned into raster images. Font mapping and mapping each character's glyph to Unicode. Xenos Developer Studio Written in Java, Xenos Developer Studio is a feature-rich Windows-based development environment for rapidly building Xenos d2e Vision application projects and all associated parameters. 12 Java Transformers Administration Guide

13 Parsers Parsers The parsers transform incoming print-streams to the Xenos Intermediate Format (XIF). XIF contains all the objects from the parsed pages, which can then be read, manipulated by other transformer components, or both. The parser evaluates your input data stream and parses it according to the parameters that have been set. The parser looks for particular values, control sequences, keywords, and other specific parameter options and passes this information to the generator to provide correct output. The parameters you set in the project file determine the following: How your input file is parsed and prepared for processing. How it is handled by the generator. How the output is provided. The parsers available include: AFP Parser, which parses input IBM AFP print-streams including MO:DCA-P, IOCA, GOCA, BCOCA, and ACIF. Metacode Parser, which parses input Xerox Metacode and LCDS, often referred to as DJDE print-streams. Pure Metacode files, line data and mixed mode files that print on Xerox Centralized printers are supported. AFP Parser The AFP Parser is designed to process and convert IBM's Advanced Function Presentation Data Streams (AFPDS) to XIF data for subsequent processing by generators. Features of the AFP Parser include: Line data and mixed mode files that print on AFP Printers through IBM Print Services Facility (PSF). Fully composed MO:DCA-P files. BCOCA Barcode Objects. Overlays, Page Segments. Single color IOCA images with Function Set 10, 11, 20, 42, and 45 support. Chapter 1: Introduction 13

14 Parsers GOCA vector graphics, including mixed CMYK and RGB color definitions. ACIF Resource files. Extraction of information from comment, NOOP, and TLE records for indexing purposes. AFP Outline Fonts. Supported for mapping only; no rasterization is done by mapping to a True Type font, such as for TIFF output. Double-byte character sets (DBCS) support and double-byte SOSI scheme (PRMODE). Bounded box fonts and core interchange family (CIF) fonts. Standard International Components for Unicode (ICU) table can be used to simplify mapping AFP encodings into Unicode. Resources, either inline or in an ACIF file, can be optionally extracted into separate files, for easier resource and data analysis. Metacode Parser The Metacode Parser is designed to process and convert Xerox Metacode and LCDS, often referred to as DJDE. Pure Metacode files, line data and mixed mode files that print on Xerox Centralized printers are supported. The Metacode Parser outputs to XIF data for subsequent processing by generators. The Metacode Parser is ideal for migrating high-volume printer applications to other high-volume print output such as IBM AFP, and to content management archives for storage and for dynamic Web presentment, in PDF, for example. Features of the Metacode Parser include: Support for line data with JSL, PDEs and CMEs. Support for LCDS, also known as DJDE. PDEs can be internal to the JSL, or external in binary format. PDEs and CMEs may be in JSL files that are preloaded with a parameter. Support for external CMEs. Support for font mapping or rasterization at a font or individual character level. Ability to specify paper stocks by name and paper size. Processing of duplex pages. Support for RFEED for paper tray selection. Support for DJDE FILE=() for Inline Resources. Comments that come from DJDEs, Hex 03 CCs, and OTEXT commands are placed into XIF and their selection can be controlled through parameters. 14 Java Transformers Administration Guide

15 Generators Generators The generators use the XIF data created by the parser and process flow components to create output in the desired particular format. To execute, generators require that you configure data and appearance translation rules, which match or correlate the fonts used in the input file with fonts used to generate the output file. The generators available include: PCL Generator Generates PCL5 output. PDF Generator Generates Adobe PDF 1.4 output. Supports standard Acrobat 128-bit security for document fraud protection. PostScript Generator Generates PostScript Level 3, suitable for printing on any PostScript Level 3 printer. PCL Generator The PCL Generator produces PCL5 output from XIF data. Output from traditional high-volume data streams can be transformed into PCL suitable for desktop or production printers. The PCL Generator provides integration with desktop and production PCL printers from legacy print-streams. Features of the PCL Generator include: Support for PCL5 output. Support for color image, text, shade and vector. Support for macro (forms/overlays from parser are output as macro) to make the output file smaller. Point sizes for fonts up to three decimal places, such as Tray size and simplex/duplex settings are passed from parser. Edge-to-edge printing. Support for edge-to-edge printing done by slightly shrinking the page image, shifting the image to the center of the page, or both. Ability to embed fonts in PCL output. Chapter 1: Introduction 15

16 Generators Limitations of the PCL Generator are: No support for PCL5e, PCL5c, or PCL6. Data verification is essential to help ensure that data-specific requirements are supported. PDF Generator The PDF Generator transforms XIF data into high-fidelity Adobe Portable Document Format (PDF) which is viewable and printable. It supports the following features: PDF documents can remain searchable with the appropriate use of Font Mapping. DBCS support available using standard Adobe CJK fonts, enabled through the use of Unicode encoding in XIF. Embedded Type 1 fonts. Embedded TrueType fonts. Dynamic creation and embedding of Type 3 fonts (with searchable text) even for double-byte Adobe CJK fonts. Overlays/Forms converted once, not each time they are used. Flate compression of text, graphics, and fonts used within a PDF. True PDF color-fill shading can be substituted for Bitmap shade patterns in the incoming documents, to improve the look of the output and reduce file sizes. Linearization, can be done in-place while generating the output PDF file, which enables better viewing over the Web, in certain circumstances, when using a browser. Standard Adobe Acrobat 128-bit encryption for document security and fraud protection. PDF is a document architecture and file format developed by Adobe. Adobe Acrobat Reader can be used to view PDF files. Adobe Acrobat Exchange can be used to both view and manipulate PDF files. The following features are available for PDF generation using the PDF Generator with other Components: Automatically generate PDF Bookmarks using the Table of Contents Component. Automatically generate URLs using the URL Link Component. Add color during processing using the Constant Print Component. Allow document breaking (multiple PDF files from a single input file) using the Document Breaking Component. 16 Java Transformers Administration Guide

17 How the Java Transformers Work PostScript Generator The PostScript Generator produces PostScript Level 3, suitable for printing on any PostScript Level 3 printer, from the XIF data. Applications include migration from Metacode and AFP to PostScript enabled printers providing integration with desktop and production PostScript printers from legacy print-streams. This component is often used to drive printers that support PostScript or applications which allow PostScript viewing. Features of the PostScript Generator include: Supports PostScript Level 3. Point sizes for fonts up to three decimal places, such as Tray size and simplex/duplex settings are passed from parser. Support for color output. Group 4 (CCITT) Image compression. Edge-to-edge printing. Support for edge-to-edge printing done by slightly shrinking the page image, shifting the image to the center of the page, or both. Support for Document Structuring Conventions (DSC) PostScript. Limitations of the PostScript Generator are: Cannot embed fonts into output. Data verification is essential to help ensure that data-specific requirements are supported. How the Java Transformers Work When CA Spool processes a report at file close, at file route, release, or re-queue time, it performs the following checks to decide if the file must be transformed: If the file has a PRMODE=x2yy transform the file, x2yy is the value of the transformer you plan to use. If the T transformer option is indicated, transform the file. If file PRMODE=PAGE, transform the file. If the file is PAGEDEF, FORMDEF, or multi CHARS, transform the file. If the C option and single CHARS is indicated, transform the file. Chapter 1: Introduction 17

18 How the Java Transformers Work If the Transformer interface was not started, do not transform. If the file was already transformed, do not transform. If the file is FCB=ASIS, do not transform. If the target printer node does not specify TRANSFRM=x2yy*, do not transform, x2yy is the value of the transformer you plan to use. If the K transformer option is indicated, and the file is held, do not transform. If the file must be transformed, CA Spool performs the following: Starts the CAIQD2E FSS STC if not already started. Queues the transformation request to a CAIQD2E transformer subtask. The CAIQD2E transformer subtask opens the input file and obtains input file attributes and optional partial print parameters. Obtains transformer options from the PRMODE or TRANSFRM parameters. Search the APP specified directory for a *.d2eproj transformer parameter file as follows: a. Search D2EPROJ=filename1.d2eproj file if specified through node DRIVPRM1-4, file OUTPUT ADDRESS or USERDATA parameters. b. Search filename2.d2eproj file where filename2 is the actual CA Spool file name. c. Search filename3.d2eproj file where filename3 is the device type name defined for the target printer node using DEFNODE statement. d. Search x2yy.d2eproj where x2yy is the actual transformer id specified through file PRMODE parameter or node TRANSFRM parameters. Opens a new output file with most of the same attributes as the input file. Queues the transformer request to the Xenos d2e Vision JVM, which reads the input file, performs the transformation using standard resources, and writes the output file. Closes the output file, which is now ready for further processing. Closes and deletes the input file unless the K keep option has been specified. More information: TRANSFRM (see page 67) Initialization Parameter Statements (see page 66) 18 Java Transformers Administration Guide

19 Features and Benefits Features and Benefits The CA Spool Java Transformers are part of a suite of CA enterprise-wide print management solutions that enable users to print any type of data on any printer. The CA Spool Java Transformers offer the following features and benefits: Provide the ability to print AFP and Metacode reports on any network attached PCL or PostScript printer. Provide the ability to automatically convert AFP and Metacode reports to PDF reports and send as attachments in directly to the users, viewed by using the CA Spool Web Interface, or passed to CA View, CA Dispatch, or CA Bundl for archiving and viewing. Provide automatic and unattended data stream transformation using standard AFP and Metacode resources. Perform the data stream transformation on the operating environment where the AFP and Metacode resources are already stored to avoid resource management on multiple operating environments and servers. Format text reports from any operating environment using AFP resources while they are translated into PCL, PostScript, or PDF documents. Protect and improve your investment in the AFP architecture by adding support for all your network attached printers. Help sites eliminate the need to use dedicated PSF printers and IPDS data stream conversion cards. Support using the same network attached PCL and PostScript printers for printing reports from any operating environment. Provide a complete software solution that you only have to buy once and that supports an unlimited number of PCL and PostScript printers. Chapter 1: Introduction 19

20

21 Chapter 2: Installing the Java Transformers This section explains how to install and set up the CA Spool Java Transformers. Note: For information about Installing Your Product Using CA MSM, see the CA Spool Installation Guide. Important! The System Configuration Service (SCS) is not available for the Java Transformers. This section contains the following topics: Software Requirements (see page 21) CA Common Services Requirements (see page 22) How CA MSM Works (see page 22) Distribution Libraries (see page 24) Target Libraries (see page 25) Concurrent Releases (see page 25) Software Requirements The following are the software prerequisites for CA Spool Java Transformers: CA Spool Release 11.7 CA Common Services (CCS) 31-bit SDK for z/os, Java Technology Edition, V6 SR5 (5655-R31) Notes: The Java transformers parameter files are all in ASCII. The support for viewing and editing of ASCII files have been improved in z/os 1.11, so ASCII file manipulation is now like working with EBCDIC files. We recommend z/os 1.11 or higher. For more information, see section z/os UNIX directory list utility line commands at /5.17.4?SHELF=ISPZPM80.bks&DT= Chapter 2: Installing the Java Transformers 21

22 CA Common Services Requirements CA Common Services Requirements We recommend that you maintain CA Common Services at a current maintenance level to ensure compatibility. For the latest information on maintenance requirements, contact CA Support Online. Note: If you intend to use CA MSM for your installation and maintenance tasks, there may be certain additional CA Common Service requirements. For more information about software requirements, see the the CA Mainframe Software Manager Product Guide. The following CA Common Services are used with CA Spool: CAIRIM CA LMP CAISDI Service CA Health Checker Common Service Note: If other CA products are installed at your site, some of these services may already be installed. How CA MSM Works CA MSM is a program that runs in the address space of an application server environment hosted on a z/os system. Typically, this system is where you use SMP/E to install and maintain your products. The system is known as the SMP/E driving system. The CA MSM web-based interface enables you to submit SMP/E batch jobs dynamically without having to code those jobs manually. 22 Java Transformers Administration Guide

23 How CA MSM Works The following illustration shows the main components and data flows: CA MSM has the following main components: CA MSM Services Provides the following services: Product Acquisition Service (PAS) Facilitates the acquisition of CA mainframe products and the service for those products, such as program temporary fixes (PTFs). The service retrieves information about the products to which your site is entitled and records these entitlements in a software inventory maintained on your driving system. The service can also download the LMP keys (licenses) for those products. The web-based interface enables you to browse the software inventory for available software and fixes, and download them from the CA Support Online website to the driving system. Chapter 2: Installing the Java Transformers 23

24 Distribution Libraries Software Installation Service (SIS) Facilitates the installation and maintenance of CA mainframe products in the software inventory of the driving system. The web-based interface enables you to browse and manage the software inventory, and automate installation tasks. You can browse downloaded software packages, and browse and manage SMP/E consolidated software inventories (CSIs) on the driving system. Software Deployment Service (SDS) Database Facilitates the deployment of CA Technologies mainframe products from the software inventory of the driving system. This service enables you to deploy installed products that are policy driven with a set of appropriate transport mechanisms across a known topology. The enterprise system topology can include shared DASD environments, networked environments, and z/os systems. Policies represent a combination of metadata input and user-supplied input. Metadata input identifies the component parts of a product. User-supplied input identifies the deployment criteria, such as where it will go and what it will be called. Stores information for use by CA MSM. Policy Stores site and user information for downloading and processing CA mainframe products. Inventory Stores information about the CA mainframe products to which you are entitled. Web-Based Interface Enables you to acquire, install, maintain, and deploy your CA mainframe products from the CA MSM catalog, and manage your SMP/E environments. The web-based interface includes online help that provides information about how to use CA MSM. Distribution Libraries Use the following table to estimate disk space for the distribution libraries that are needed to install CA Spool. Library Name Blksize TRKS Dir. Blks Description CAI.AE0CDATA Data Library CAI.AE0CXML CA MSM Deployment and Configuration Services 24 Java Transformers Administration Guide

25 Target Libraries Target Libraries Note: Allocate these libraries only if they do not already exist. Use the following table to estimate disk space for the target libraries that are needed to install CA Spool. Library Name Blksize TRKS Dir. Blks Description CAI.CE0CDATA Data Library CAI.CE0CXML CA MSM Deployment and Configuration Services Concurrent Releases You can install this release of CA Spool and continue to use an older release for your production environment. If you plan to continue to run a previous release, consider the following points: When installing into an existing SMP/E environment, this installation deletes previous releases. If you acquired your product from tape or with Pax-Enhanced ESD, select different target and distribution zones for your new release from where your current release is installed. The new zones use different libraries than your current release. Note: CA MSM installs into a new CSI by default. Define DDDEF entries in your new zones to point SMP/E to the proper libraries for installation. Ensure that they point to the new release libraries. Chapter 2: Installing the Java Transformers 25

26

27 Chapter 3: Installing Your Product from Pax-Enhanced ESD This section contains the following topics: How to Install a Product Using Pax-Enhanced ESD (see page 27) Allocate and Mount a File System (see page 33) Copy the Product Pax Files into Your USS Directory (see page 36) Create a Product Directory from the Pax File (see page 41) Copy Installation Files to z/os Data Sets (see page 42) Receiving the SMP/E Package (see page 43) Clean Up the USS Directory (see page 47) Apply Maintenance (see page 48) How to Install a Product Using Pax-Enhanced ESD This section describes the Pax-Enhanced ESD process. We recommend that you read this overview and follow the entire procedure the first time you complete a Pax-Enhanced ESD installation. For experienced UNIX users, the Pax-Enhanced ESD Quick Reference Guide has sufficient information for subsequent installations. Important! Downloading pax files for the SMP/E installation as part of the Pax-Enhanced ESD process requires write authority to the UNIX System Services (USS) directories used for the ESD process. If you prefer not to involve all CA Technologies product installers with z/os UNIX System Services, assign a group familiar with USS to perform Steps 1 through 4 and provide the list of the unpacked MVS data sets to the product installer. USS is not required for the actual SMP/E RECEIVE of the product or for any of the remaining installation steps. To install files using Pax-Enhanced ESD, use the following process: 1. Allocate and mount the file system. This process requires a USS directory to receive the pax file and to perform the unpack steps. We recommend that you allocate and mount a file system dedicated to Pax-Enhanced ESD and create the directory in this file system. Ensure that all users who will be working with pax files have write authority to the directory. Chapter 3: Installing Your Product from Pax-Enhanced ESD 27

28 How to Install a Product Using Pax-Enhanced ESD 2. Copy the product pax files into your USS directory. To download files, choose one of the following options: Download a zip file from CA Support Online to your PC, unzip the file, and then upload the product pax files to your USS file system. FTP the pax files from CA Support Online directly to your USS directory. Note: Perform Steps 3 through 6 for each pax file that you upload to your USS directory. 3. Create a product directory from the pax file. Set the current working directory to the directory containing the pax file, and create a new directory in your USS directory by entering the following command: pax -rvf pax-filename 4. Use the SMP/E GIMUNZIP utility to create z/os installation data sets. The file UNZIPJCL in the directory created by the pax command in Step 3 contains a sample job to GIMUNZIP the installation package. Edit and submit the UNZIPJCL job. 5. Receive the SMP/E package. For this step, use the data sets created by GIMUNZIP in Step 4. Perform a standard SMP/E RECEIVE using the SMPPTFIN and SMPHOLD (if applicable) DASD data sets. Also, specify the high-level qualifier for the RELFILEs on the RFPREFIX parameter of the RECEIVE command. 6. Proceed with product installation. Consult product-specific documentation, including AREADME files and installation notes to complete the product installation. 7. (Optional) Clean up the USS directory. Delete the pax file, the directory created by the pax command, all of the files in it, and the SMP/E RELFILEs, SMPMCS, and HOLDDATA data sets. More Information: USS Environment Setup (see page 32) Allocate and Mount a File System (see page 33) Copy the Product Pax Files into Your USS Directory (see page 36) Create a Product Directory from the Pax File (see page 41) Copy Installation Files to z/os Data Sets (see page 42) 28 Java Transformers Administration Guide

29 How to Install a Product Using Pax-Enhanced ESD How the Pax-Enhanced ESD Download Works Important! To download pax files for the SMP/E installation as part of the Pax-Enhanced ESD process, you must have write authority to the UNIX System Services (USS) directories used for the ESD process and available USS file space before you start the procedures in this guide. Use the following process to download files using Pax-Enhanced ESD: 1. Log in to and click Download Center. The CA Support Online web page appears. 2. Under Download Center, select Products from the first drop-down list, and specify the product, release, and genlevel (if applicable), and click Go. The CA Product Download window appears. 3. Download an entire CA Technologies product software package or individual pax files to your PC or mainframe. If you download a zip file, you must unzip it before continuing. For both options, The ESD Product Download Window (see page 29) topic explains how the download interface works. Note: For traditional installation downloads, see the Traditional ESD User Guide. Go to log in, and click Download Center. A link to the guide appears under the Download Help heading. 4. Perform the steps to install the product based on the product-specific steps. The product is installed on the mainframe. ESD Product Download Window CA Technologies product ESD packages can be downloaded multiple ways. Your choices depend on the size of the individual files and the number of files you want to download. You can download the complete product with all components or you can select individual pax and documentation files for your product or component. Chapter 3: Installing Your Product from Pax-Enhanced ESD 29

30 How to Install a Product Using Pax-Enhanced ESD The following illustration shows sample product files. It lists all components of the product. You can use the Download Cart by checking one or more components that you need or check the box for Add All to cart. If you prefer to immediately download a component, click the Download link. Clicking the link for an individual component takes you to the Download Method page. 30 Java Transformers Administration Guide

31 How to Install a Product Using Pax-Enhanced ESD Depending on the size and quantity of product files ordered, the Download Method screen could also have these options: Note: For mainframe downloads using this HTTP method, click the Learn More link. Chapter 3: Installing Your Product from Pax-Enhanced ESD 31

32 How to Install a Product Using Pax-Enhanced ESD The HTTP method lets you start downloading immediately. The FTP method takes you to the Review Orders page that displays your order, first in a Pending status changing to Ready when your order has been processed. Preferred FTP uses the new content delivery network (CDN). Alternate FTP uses the CA Technologies New York-based FTP servers. The Create a Zip File option first creates the zip, and when ready, offers the options shown by the Zip Download Request examples in the next screen. USS Environment Setup You need a UNIX System Services (USS) directory and a file system with adequate space to perform the following tasks: Receive product pax files from CA Support Online. Perform utility functions to unpack the pax file into MVS data sets that you can use to complete the product installation. 32 Java Transformers Administration Guide

33 Allocate and Mount a File System We recommend that you allocate and mount a file system dedicated to Pax-Enhanced ESD. The amount of space that you need for the file system depends on the following variables: The size of the pax files that you intend to download. Whether you plan to keep the pax files after unpacking them. We do not recommend this practice. We recommend that you use one directory for downloading and unpacking pax files. Reusing the same directory minimizes USS setup. You need to complete the USS setup only one time. You reuse the same directory for subsequent downloads. Alternatively, you can create a new directory for each pax download. Important! Downloading pax files for the SMP/E installation as part of the Pax-Enhanced ESD process requires write authority to the UNIX System Services (USS) directories used for the ESD process. In the file system that contains the ESD directories, you also need free space approximately 3.5 times the pax file size to download the pax file and unpack its contents. For example, to download and unpack a 14 MB pax file, you need approximately 49 MB of free space in the file system hosting your ESD directory. Allocate and Mount a File System You can use the zseries File System (zfs) or hierarchical file system (HFS) for ESD downloads. This procedure describes how to perform the following tasks: Allocate a zfs or an HFS. Create a mount point in an existing maintenance USS directory of your choice. Mount the file system on the newly created mount point. Note: You must have SUPERUSER authority to do this. Optionally, permit write access to anyone in the same group as the person who created the directory. Important! USS commands are case-sensitive. Chapter 3: Installing Your Product from Pax-Enhanced ESD 33

34 Allocate and Mount a File System Follow these steps: 1. Allocate the file system by customizing one of the following samples to your site's requirements: On a zfs, use the following sample: //DEFINE //SYSPRINT DD //SYSUDUMP DD //AMSDUMP DD //SYSIN DD * /* EXEC PGM=IDCAMS SYSOUT=* SYSOUT=* SYSOUT=* DEFINE CLUSTER ( + NAME(your_zFS_dataset_name) + STORAGECLASS(class) + LINEAR + CYL(primary secondary) + SHAREOPTIONS(3,3) + ) //FORMAT EXEC PGM=IOEAGFMT,REGION=0M, // PARM=('-aggregate your_zfs_dataset_name -compat') //SYSPRINT DD //SYSUDUMP DD SYSOUT=* SYSOUT=* //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //CEEDUMP DD //* SYSOUT=* On an HFS, use the following sample: //ALCHFS EXEC PGM=IEFBR14 //CAESD DD DSN=yourHFS_dataset_name, // DISP=(NEW,CATLG,DELETE),UNIT=3390, // DSNTYPE=HFS,SPACE=(CYL,(primary,secondary,1)) The file system is allocated. Note: Ensure that the zfs or HFS data set name that you use conforms to your data set naming conventions for USS file systems. If the allocation of the file system data set fails, it is because of environmental settings not allowing for the allocation. On an HFS, try using the ISPF 3.2 Data Set Utility to allocate your HFS data set. 34 Java Transformers Administration Guide

35 Allocate and Mount a File System 2. Create a mount point for the file system. This example shows how to create a /CA/CAESD directory in an existing directory, /u/maint. From the TSO OMVS shell, enter the following commands: cd /u/maint/ mkdir CA cd CA mkdir CAESD Note: This document refers to this structure as yourussesddirectory. The mount point is created. 3. Mount the file system by customizing one of the following samples to your site's requirements: On a zfs, use the following sample: MOUNT FILESYSTEM('your_zFS_dataset_name') MOUNTPOINT('yourUSSESDdirectory') TYPE(ZFS) MODE(RDWR) PARM(AGGRGROW) On an HFS, use the following sample: MOUNT FILESYSTEM('your_HFS_dataset_name') MOUNTPOINT('yourUSSESDdirectory') TYPE(HFS) MODE(RDWR) The file system is mounted. 4. (Optional) Set security permissions for the directory. You can use the chmod command to let other users access the ESD directory and its files. For example, to allow write access to the ESD directory for other users in your USS group, from the TSO OMVS shell, enter the following command: chmod -R 775 /yourussesddirectory/ Write access is granted. Note: For more information about the chmod command, see the IBM z/os UNIX System Services User Guide (SA ). Chapter 3: Installing Your Product from Pax-Enhanced ESD 35

36 Copy the Product Pax Files into Your USS Directory Copy the Product Pax Files into Your USS Directory To begin the CA Technologies product installation procedure, copy the product's pax file into the USS directory you set up. Use one of the following methods: Download the product pax files directly from the CA Support Online FTP server to your z/os system. Download the product pax file from the CA Support Online FTP server to your PC, and upload it to your z/os system. Download the product file from CA Support Online to your PC. If your download included a zip file, unzip the file, and upload the unzipped pax files to your z/os system. This section includes a sample batch job to download a product pax file from the CA Support Online FTP server directly to a USS directory on your z/os system and sample commands to upload a pax file from your PC to a USS directory on your z/os system. Important! The FTP procedures vary due to local firewall and other security settings. Consult your local network administrators to determine the appropriate FTP procedure to use at your site. Ensure that sufficient free space is available in the USS file system you are using for Pax-Enhanced ESD to hold the product pax file. If you do not have sufficient free space, error messages similar to the following appear: EZA1490I Error writing to data set EZA2606W File I/O error 133 When the download finishes, the pax file size in your USS directory matches the value in the Size column for the corresponding pax file on the CA Technologies Products Download window. More Information: How the Pax-Enhanced ESD Download Works (see page 29) ESD Product Download Window (see page 29) 36 Java Transformers Administration Guide

37 Copy the Product Pax Files into Your USS Directory Download Using Batch JCL Use this process to download a pax file from the CA Support Product Downloads window by running batch JCL on the mainframe. Use the sample JCL attached to the PDF file as CAtoMainframe.txt to perform the download. Important! To simplify the Pax-Enhanced ESD process, the PDF version of this guide includes a sample JCL job that you can copy directly to the mainframe. To access this job, click the paper clip icon in the lower left corner of the PDF reader. This opens a window displaying attachments. Double-click the file to view the sample JCL. Note: We recommend that you follow the preferred method as described on CA Support Online. This procedure is our preferred download method; however, we do include the procedure to download to the mainframe through a PC in the next section. Follow these steps: 1. Supply a valid JOB statement. 2. Replace yourtcpip.profile.dataset with the name of the TCP/IP profile data set for your system. Consult your local network administrators, if necessary. The job points to your profile. 3. Replace Your Address with your address. The job points to your address. 4. Replace yourussesddirectory with the name of the USS directory that you use for ESD downloads. The job points to your USS directory. 5. Locate the product component to download on the CA Support Product Download window. You have identified the product component to download. 6. Click Download for the applicable file. Note: For multiple downloads, add files to a cart. The Download Method window opens. 7. Click FTP Request. The Review Download Requests window displays any files that you have requested to download. Note: We send you an when the file is ready to download or a link appears in this window when the file is available. Chapter 3: Installing Your Product from Pax-Enhanced ESD 37

38 Copy the Product Pax Files into Your USS Directory 8. Select one of the following methods: Preferred FTP Uses CA Technologies worldwide content delivery network (CDN). If you are not able to download using the Preferred FTP method, check the security restrictions for all servers that company employees can download from that are outside of your corporate network. Host Name: ftp://ftpdownloads.ca.com Alternate FTP Uses the original download servers that are based on Long Island, New York. Host Name: ftp://scftpd.ca.com for product files and download cart files and ftp://ftp.ca.com for individual solution files. Both methods display the host, user name, password, and FTP location, which you then can copy into the sample JCL. Note: For details regarding FTP, see the FTP Help document link in the Review Download Requests window and the Learn More link available in the Download Methods window. 9. Submit the job. Important! If your FTP commands are incorrect, it is possible for this job to fail and still return a zero condition code. Read the messages in the job DDNAME SYSPRINT to verify the FTP succeeded. After running the JCL, the pax file resides in the mainframe USS directory that you supplied. 38 Java Transformers Administration Guide

39 Copy the Product Pax Files into Your USS Directory Example: CAtoMainframe.txt, JCL The following text appears in the attached CAtoMainframe.txt JCL file: //GETPAX JOB (ACCOUNTNO),'FTP GET ESD PACKAGE', // MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID //********************************************************************* //* This sample job can be used to download a pax file directly from * //* CA Support Online to a USS directory on your z/os system. * //* * //* When editing the JCL ensure that you do not have sequence numbers * //* turned on. * //* * //* This job must be customized as follows: * //* 1. Supply a valid JOB statement. * //* 2. The SYSTCPD and SYSFTPD JCL DD s statements in this JCL maybe * //* optional at your site. Remove the statements that are not * //* required. For the required statements, update the data set * //* names with the correct site specific data set names. * //* 3. Replace "Host" based on the type of download method. * //* 4. Replace "Your Address" with your address. * //* 5. Replace "yourussesddirectory" with the name of the USS * //* directory used on your system for ESD downloads. * //* 6. Replace "FTP Location" with the complete path * //* and name of the pax file obtained from the FTP location * //* of the product download page. * //********************************************************************* //GETPAX EXEC PGM=FTP,REGION=0K //SYSTCPD DD DSN=yourTCPIP.PROFILE.dataset,DISP=SHR //SYSFTPD DD DSN=yourFTP.DATA.dataset,DISP=SHR //SYSPRINT DD SYSOUT=* //OUTPUT DD SYSOUT=* //INPUT DD * Host anonymous Your Address lcd yourussesddirectory binary get FTP location quit Chapter 3: Installing Your Product from Pax-Enhanced ESD 39

40 Copy the Product Pax Files into Your USS Directory Download Files to Mainframe through a PC Example: FTP Commands If you download pax or zip files from CA Support Online to your PC, use this procedure to upload the pax file from your PC to your z/os USS directory. Follow these steps: 1. Follow the procedures in How the Pax-Enhanced ESD Download Works to download the product pax or zip file to your PC. If you download a zip file, first unzip the file to use the product pax files. The pax or zip file resides on your PC. 2. Open a Windows command prompt. The command prompt appears. 3. Customize and enter the FTP commands with the following changes: a. Replace mainframe with the z/os system's IP address or DNS name. b. Replace userid with your z/os user ID. c. Replace password with your z/os password. d. Replace C:\PC\folder\for\thePAXfile with the location of the pax file on your PC. e. Replace yourussesddirectory with the name of the USS directory that you use for ESD downloads. f. Replace paxfile.pax.z with the name of the pax file to upload. The pax file is transferred to the mainframe. This list is a sample of FTP commands to upload the pax file from your PC to your USS Pax-Enhanced ESD directory: ftp mainframe userid password bin lcd C:\PC\folder\for\thePAXfile cd /yourussesddirectory/ put paxfile.pax.z quit exit 40 Java Transformers Administration Guide