Creating server

Edit online

This section contains the information required to declare variables and trigger the JCL jobs.

Procedure

After the workflow is created, perform the following tasks to create a server.

  1. Click Declare parameters and then Perform. Provide the following values:
    • High level qualifier: - Data Virtualization Manager product library: Name of the product library e.g. CSD.QA.AVZ.
    • High level qualifier for IN00: - Data Virtualization Manager server initilialization library: Name of the IN00 file e.g. HLQ.SAVZEXEC.
    • High level qualifier for INEF: - Data Virtualization Manager server initilialization library: Name of the INEF file e.g. HLQ.SAVZEXEC.
    • High level qualifier for PROC: - Data Virtualization Manager server procedure library: Name of the procedure library e.g. HLQ.PROCLIB.
    • APF Authorization DSN LIB 1: - Data Virtualization Manager Server APF for 1st DSN LIB name: APF authorization library name e.g. HLQ.SAVZLOAD.
    • APF Authorization DSN LIB 2: - Data Virtualization Manager Server APF for 2nd DSN LIB name: APF authorization library name e.g. HLQ.SAVZRPC.
    • Server started task identifier: - Started task ID: Name of the created server e.g. AVZA
    • UNIT: - DASD unit for work data set: The type of unit to use for allocating temporary data sets. The valid values are SYSDA, SYSALLDA, VIO, and the default value is SYSDA.
    • UNIT: - DASD unit for CREATE data set: The type of unit to use for allocating temporary data sets. The valid values are SYSDA, SYSALLDA, VIO, and the default value is SYSALLDA.
    • Region size: - Region size the server will use: The region size of the server. The default value is 0M.
    • Virtual storage: - Virtual storage above the bar: The virtual storage in megabytes, for the server. The default value is 200M.
    Click Next, and provide the following values.
    • Trace file primary quantity: - Trace file primary space allocation: Trace file primary quantity in cylinders.
    • Trace file secondary quantity: - Trace file secondary space allocation: Trace file secondary quantity in cylinders.
    • Global variable checkpoint file primary quantity: - Global variable checkpoint file primary space allocation: Global variable checkpoint file primary quantity in cylinders.
    • Global variable checkpoint file secondary quantity: - Global variable checkpoint file secondary space allocation: Global variable checkpoint file secondary quantity in cylinders.
    • Maximum number of messages: - Maximum messages: Trace file message size.
    • IN00 configuration member: - Started task IN00: Product initialization REXX program. The default value is AVZSIN00.
    • Server started task identifier: - Started task INEF: Sample SEF initialization REXX program. The default value is AVZ1INEF.
    • Proc configuration member: - Started task PROC: Creates a member to generate proc for the user.
    • Server proc name: - Server started task proc name: Server task proc name. This value is mandatory, and the default value is AVZ1PROC.
    • TCP/IP OE Port: - OE Port Number: Listening TCP/IP port number for the server. This value is required.
    • Web Services Port: - Web Services Port: Web Service port number that the studio client uses to communicate with the server. This value is required. The default value is 1201.
    • SMF record number: - SMF Record Number: Indicates the SMF record type to be created. This value is optional, and the default value is 249.
    • Enable IAM support: - Enable support for IAM VSAM files: This parameter specifies whether to call the interface module for IAM support to analyze keys and set ranges for MapReduce. Valid values are Yes and No, and the default value is No.
    Click Next, and provide the following values.
    • Db2 high level qualifier: - Db2 subsystem library: Library for Db2 subsystem.
    • Db2 SSID: - Db2 Subsystem Identifier : Db2 subsystem name. The default value is DSN1.
    • Subsystem port number: - Db2 subsystem port number: Port number for DRDA access. This value is required, and the default value is 443.
    • Db2 DDF Status: - Db2 Subsystem Status : DDF status to Db2 database subsystems. The default value is ENABLE.
    • Db2 DDF Location: - Db2 Subsystem Location : Location of the Db2 subsystem, and the default value is DEV1DSN1.
    • Domain name: - Subsystem domain name: Domain name of the Db2 subsystem being configured. This value is optional, and the default value is DB2DOMAIN.
    • CCSID value: - Db2 subsystem CCSID value: CCSID value of the Db2 subsystem being configured. The CCSID value can be found in the Db2 installation panel DSNTIPF, option 7. The default value is 37.
    • LU Name: - Dbe subsystem LU name: LU name of the Db2 subsystem to be used for RACF pass ticket generation. This value can be found in the master address space of the subsystem configured or by issuing the command DISPLAY DDF. The default value is DSN1LU.
    • Bind owner: - Db2 plan BIND owner: Db2 user ID used as the owner in the BIND job. The default value is DB2USER.
    • Bind collection ID: - Db2 collection identifier: Collection ID for the DRDA packages used by the server. Use this value in the AVZ studio when setting up the connection to the server. The default is DB2USER.
    • Db2 connection ID: - Db2 connection identifier: Connection ID to use in the BIND job for connecting to Db2 subsystems on z/OS. The default value is DSN1.
    • Db2 SDSNCONNID: - Db2 SDSNCONNID library: SDSNEXIT library to use while binding packages. This value is required if Db2 is the data source. The default value is DSN1.
    • Db2 SDSNSNETP2: - Db2 SDSNSNETP2 library: Db2 plan name. The default value is DSNTIAD.
    • JOBLIB DSNSYS: - JOBLIB DSNSYS library: Db2 subsystem name. The default value is DSN1.
    Click Next and then Finish
  2. For the steps 2-7, perform the following.
    • Click the step name and then click Perform.
    • Review the JCL and modify it if required. Check the box All steps in workflow 'workflow_name'. if the changes should be reflected in all steps or check the box This step 'step_name' only. if the changes should be reflected only in this step. workflow_name is the name of the created workflow, and the step_name is the name of the current step.
    • Click Next. Edit the JCL if required.
    • Click Next.
    • Check Submit JCL to submit the JCL file and/or check Save JCL to save the JCL file as z/OS UNIX file or z/OS data set.
    • Click Finish to submit and/or save the JCL file.

Results

Once you complete the steps 1-7, the JCL files are submitted and the server with the given settings is created.