Skip to main content

 
IBM Systems >  System z >  Operating systems  > 

What's new in SMP/E for z/OS V3R3


   
 

New entry name wildcard capability available on the CSI Query dialog panel (GIMQU1PO)

You can now leave blank or enter a wild card in the Entry Name field of the CSI Query dialog panel (GIMQU1PO) to display a selection list of of all the SYSMOD entries in the specified target zone.



New default parameters sent to copy utility: SPCLCMOD and CMWA

SMP/E passes new default parameters (SPCLCMOD and CMWA=256K) to the copy utility when copying modules, load modules, or programs.



Extended RECEIVE SOURCEID processing

The RECEIVE command now assigns the source ID specified on the SOURCEID operand of the command to SYSMODs found in the SMPPTFIN input stream, even if the SYSMOD is already received.



New GIMGTPKG service routine

You can use the new GIMGTPKG service routine to get GIMZIP packages from a remote FTP server in a TCP/IP network and store the package on a local z/OS host. GIMGTPKG performs the functions of the SMP/E RECEIVE FROMNETWORK TRANSFERONLY command, but does so independently of SMP/E. It uses FTP to transport the files of a GIMZIP package from a remote FTP server to a local host, thus providing:

  • Industry standard FTP protocol
  • Secure transmission using the capabilities of the z/OS FTP client
  • Ensured integrity of the transported files



Enhancements to GIMZIP and GIMUNZIP service routines

Formerly GIMZIP could create and GIMUNZIP could process packages that contained only sequential and partitioned data sets. Also, GIMUNZIP would only extract data from an archive file into a new data set allocated directly by GIMUNZIP. These service routines have been enhanced for SMP/E V3R3, as follows:

  • Packages may now contain VSAM data sets and UNIX files and directories

  • You may assign a unique id to an archive during GIMZIP processing and then use that id to identify the archive that is to be unzipped during GIMUNZIP processing

  • GIMUNZIP now allows GIMUNZIP operations into existing data sets. GIMUNZIP determines if the data set specified on the tag already exists. If the data set already exists, GIMUNZIP copies the archive file into the existing data set. If the data set does not already exist, GIMUNZIP allocates a new data set and then copies the archive file into that new data set



RECEIVE FROMNETWORK FTP interface enhancements

RECEIVE FROMNETWORK has been enhanced to:

  • Allow user credentials and file data transferred between an FTP client and server to be secured with respect to encryption, authentication, and data integrity using the Transport Layer Security (TLS) enablement for FTP

  • Allow the z/OS FTP client to connect to FTP servers that reside beyond a firewall that runs a SOCKS server

  • Make IPv6 connectivity possible for both the FTP client and server

  • Use the FTP.DATA configuration data set to allow the client to specify local site parameters. The FTP.DATA configuration data set is optional, but must be used by the client to specify the parameters for TLS security and SOCKS firewall support.

There are the following migration tasks:

  1. SMP/E will now use the FTP.DATA configuration data set to allow the client to specify local site parameters. Two of the values specified in the FTP.DATA data set are FWFriendly and FTPKEEPALIVE. These values correspond to the pasv and keepalive attributes in the CLIENT data set. Therefore, these attributes should no longer be specified in the CLIENT data set. If the pasv and keepalive attributes are specified in the CLIENT data set, they will be ignored. If required, these values must be specified in the FTP.DATA data set. Refer to z/OS Communications Server: IP User's Guide and Commands for more information about the statements that can be coded in the FTP.DATA data set.

  2. To enable TLS security, SOCKS firewall support, and IPv6 addressing, ensure that z/OS Communications Server V1R2 (or higher) is installed.

  3. If you previously specified FTP commands to navigate your local firewall using the tag of the CLIENT data set, then you may need to update them. Specifically, subcommands such as USER, PASS, and ACCT should no longer be specified in . The commands you specify in the tags should be the same as those you use with the z/OS Communications Server FTP client, and should contain only the actual values (or the appropriate substitution variables) for userid, password, and account.



REJECT command

A new CHECK operand has been added to the REJECT command The REJECT CHECK indicates whether SMP/E should do a trial run of a command without actually updating any libraries. This is a way to test for errors that might occur during actual processing and to receive reports on the changes that would be made.



Contact z/OS
Send us your questions and comments.

Resources

SMP/E home page

What's new
| V3.6 | V3.5 |
| V3.4 | V3.3 |
| V3.2 | V3.1 |
| V2.7 |