Define the CLIENT Input for RECEIVE ORDER

This article defines the command options to define the CLIENT Input for RECEIVE ORDER.
cmcm
This article defines the command options to define the CLIENT Input for RECEIVE ORDER.
Define the CLIENT Input
The SMP/E RECEIVE ORDER command uses the CLIENT data set to provide information about the local z/OS system and network, and certain processing options. The information is described using the <CLIENT> tag and attributes that are defined in detail in SMP/E for z/OS Commands in the IBM documentation. Here is an example:
<CLIENT downloadmethod="https" javahome="/usr/lpp/java/J8.0" classpath="/usr/lpp/smp/classes" javadebugoptions="-Dcom.ibm.smp.debug=severe -showversion" > <HTTPPROXY host="local.httpproxy.com"> </HTTPPROXY> <FIREWALL> <SERVER host="local.ftpproxy.com"> </SERVER> <FIRECMD>&REMOTE_USER;@&REMOTE_HOST;</FIRECMD> <FIRECMD>&REMOTE_PW;</FIRECMD> </FIREWALL> </CLIENT>
Not all tags and attributes that appear in the example are required for every user, but they are explained later in this article. The options of the CLIENT data set can be grouped into three categories: options that affect Java, options that affect HTTPS, and options that affect downloads. 
  • downloadmethod
    Identifies the network protocol to use for downloading files from the CA Download server to the local z/OS. Specify a value of https to specify HTTPS as the download method. This field is required.
  • downloadkeyring
    Identifies the location of the certificate authority certificates that are required for the Secure Sockets Layer (SSL) handshake with the HTTPS server. The name for a security manager key ring, or the keyword javatruststore may be specified.
  • javahome
    Specifies the location for the Java runtime to be used by SMP/E, which uses the capabilities of Java 8 for its HTTPS operations. Therefore, specify the location for the IBM 31-bit SDK for z/OS, Java Technology Edition Version 6 (5655-R31), or the IBM 64-bit SDK for z/OS, Java Technology Edition Version 8 (5655-R32), or a logical successor, on the javahome attribute. For more information, see the following section on Options that Affect Java.
  • <HTTPPROXY>
    Optional tags are available to describe local HTTP or SOCKS proxy servers. A proxy server redirects HTTP requests to the CA Download Server. The <HTTPPROXY> tag is used to identify a local HTTP proxy server, and the <HTTPSOCKSPROXY> tag is used to identify a local SOCKS proxy server. For more information, see the following section on Options that Affect HTTPS Operations.
Options that Affect Java
To support the HTTPS communications with the CA Automated Order Server, SMP/E uses the capabilities of Java 8. SMP/E requires IBM 31-bit SDK for z/OS, Java Technology Edition Version 6 (5655-R31), or the IBM 64-bit SDK for z/OS, Java Technology Edition Version 6 (5655-R32), or a logical successor. SMP/E supplies several Java application classes, which after SMP/E is installed, reside in the/usr/lpp/smp/classes directory in the UNIX file system on the z/OS system. For SMP/E to use these application classes, they and the Java runtime must be available in the execution environment for SMP/E. Because neither can be accessed using a STEPLIB DD statement, you specify the locations for the Java runtime and the SMP/E application classes using the javahome and classpath attributes in the CLIENT data set. The javahome attribute is used to specify the directory where the Java run time resides. The classpath attribute is used to specify the search path for Java application classes. For example:
javahome="/usr/lpp/java/J8.0" classpath="/usr/lpp/smp/classes"
If the SMP/E Java application classes are not installed on the driving z/OS system’s UNIX file system, you can use appropriate mount points and directory structure to point to a target system’s directories where SMP/E is installed. This option is useful if you use STEPLIB to access a target system’s base SMP/E programs to ensure the base SMP/E programs and the application classes are at the same service level. For example:
classpath="/TGTSYS/usr/lpp/smp/classes"
As an alternative to the javahome and classpath attributes in the CLIENT data set, use the SMPJHOME and SMPCPATH DD statements or DDDEF entries to specify the location of the Java run time and the SMP/E application classes. If specified, the SMPJHOME and SMPCPATH DD statements override any values that are specified on the javahome and classpath attributes. For example: 
//SMPJHOME DD PATH=’/usr/lpp/java/J8.0’ //SMPCPATH DD PATH=’/usr/lpp/smp/classes’
The javadebugoptions attribute is used to specify any Java command-line parameters, including debug and trace options. Such options determine what debug and trace information should be produced when SMP/E invokes its Java application classes. The debug and trace information is written to the PRINT file for the HFSCOPY utility (SYSPRINT is the default). Although it is not necessary all the time, it is a good idea when first using the RECEIVE ORDER command, to specify the following value to ensure that basic debug and trace information is produced for reference:
javadebugoptions="-Dcom.ibm.smp.debug=severe -showversion"
 
Optionally, you can specify other Java command-line parameters that affect the operation of the Java Virtual Machine (JVM). For example, if you encounter a Java error that indicates insufficient space in the Javaheap, specify an option to override the default maximum Java heap size:
javadebugoptions="-Xmx128m"
Options that Affect HTTPS Operations
SMP/E communicates with the CA Automated Order Server using the HTTP 1.1 protocol using SSL, also known as HTTPS. All communications with the server are performed using the HTTPS port of 443. Optional tags are available in the CLIENT data set for the RECEIVE ORDER command to describe local HTTP or SOCKS proxy servers. A proxy server redirects HTTP requests to the CA Automated Order Server. The <HTTPPROXY> tag identifies a local HTTP proxy server. The <HTTPSOCKSPROXY> tag identifies a local SOCKS proxy server. For example:
<HTTPPROXY host="local.httpproxy.com"> </HTTPPROXY>
The <HTTPPROXY> and <HTTPSOCKSPROXY> tags are optional. Only specify them if the HTTP requests to the Internet from your z/OS system are required to pass through a specific HTTP or SOCKS proxy server. For example, if you must specify a proxy server in your internet browser configuration to give you access to websites on the Internet, you might need to specify the <HTTPPROXY> or <HTTPSOCKSPROXY> tag in the CLIENT data set. If your HTTP or SOCKS proxy server requires authentication, use the user and pw attributes to specify the proxy server user ID and password. If your HTTP or SOCKS proxy server listens on a port other than ports 80 and 1080, use the port attribute to specify an alternate port value. For example:
<HTTPPROXY host="local.httpproxy.com" user="userid" pw="password" port="8080"> </HTTPPROXY>
For complete details of the <HTTPPROXY> and <HTTPSOCKSPROXY> tags and attributes, see SMP/E for z/OS Commands in the IBM documentation. Also, consult your network administrator for help determining what you must specify for an HTTP or SOCKS proxy server.
Options that Affect Download Operations
SMP/E uses HTTPS to communicate with the CA Automated Order Server. SMP/E also uses HTTPS to download package files containing PTFs and HOLDDATA from the CA Download server to your local z/OS system. After the package files are staged to the CA Download server, the CA Automated Delivery Request server provides SMP/E with the information to authenticate with the CA Download server and then download the package files. Specifically, it provides SMP/E with the CA Download server host name and a user ID and password for that server, which are unique for the specific package to be downloaded.
The downloadmethod attribute in the CLIENT data set tells SMP/E the method to use to download the package files from the server to your local z/OS. The CA Download server requires the use of a secure and encrypted download method, HTTPS, to download package files to your local z/OS system.