|
|
|
zIIP is a special processor that is restricted to executing specific types of SRB mode work. zIIP is intended to free up general computing capacity and lower the overall cost of computing for CPU intensive workloads.
Release 11.6 of CA XCOM Data Transport allows for offloading workload onto zIIP processors to reduce CPU utilization costs that are associated with file transfers. Initially data compression and de-compression functions are offloaded to zIIP when available and feasible, as they are highly CPU intensive functions.
CA XCOM Data Transport attempts to offload data compression and de-compression functions to a zIIP when available. Given that data compression accounts for a significant portion of CPU utilization for a data transfer, moving this processing to a zIIP reduces utilization and costs.
Enabling CA XCOM Data Transport to utilize zIIP support requires that the installation has CA Common Services for z/OS installed at the r11 release or higher. An APAR is required to be installed for both the r11 and r12 releases of CA Common Services for z/OS which introduces the zIIP Enablement Service. For the r11 release, APAR RO27636 must be installed. For the r12 release, RO27110 must be installed. The common services library must be available to the XCOM Server started task or XCOMJOB TYPE=EXECUTE job.
By default, CA XCOM Data Transport enables zIIP support providing that the zIIP Enablement Service is available to load. A new PARM and configuration parameter can be specified to disable the zIIP support. The parameter is ZIIP=YES|NO, with YES being the default.
To insure that data compression functions are eligible to be moved to the zIIP without impacting performance. CA XCOM Data Transport requires that the size of the data block being compressed or de-compressed is a minimum of 4096 (4 K) bytes. This minimum size is to insure that the overhead of switching the workload to the zIIP does not affect performance of the transfer.
We recommend that the configuration parameter MAXPACK is set to a minimum of 4096. The higher the value for these parameters, the more efficient the use of zIIP is.
For any transfer, PACK=LENGTH is specified to insure that the 4-K minimum size for compression on the zIIP is realized. Without this parameter, the record size of data in a file would need to be 4 K to move the compression workload to the zIIP.
CA XCOM Data Transport provides some facilities for managing and monitoring zIIP usage. The only goal of utilizing zIIP is to reduce CPU utilization and therefore the costs that are associated with that utilization.
For each transfer, statistics about CPU and zIIP usage are written into the history record and SMF record. This data is retrieved from the zIIP Enablement Services component of CA Common Services. This data consists of six fields which can then be reported on through a TYPE=HISTORY job and supplied CA Easytrieve reports.
A new modify command for the CA XCOM Data Transport Server is being provided to both report on status and allow zIIP support to be enabled/disabled.
The ZIIP,STATUS command provides information about the CPUs (standard and zIIP) as to how many are defined and online. The command also displays the status of zIIP support for the various features of CA XCOM Data Transport that can exploit use of zIIP. This command is the only data compression currently. Finally, statistics are displayed which show the total amount of processing time that was eligible to run on zIIP and that executed on zIIP.
The STATUS command is also issued on startup and termination of the CA XCOM Data Transport Server and XCOMJOB TYPE=EXECUTE start and termination.
The ZIIP,ENABLE and ZIIP,DISABLE commands allow an administrator to either enable or disable the zIIP support for future data transfers. Any transfers currently in progress continues to operate in the state that was active at the start of the transfer.
If an abend occurs while the transfer is running on a zIIP, CA XCOM Data Transport handles the abend. CA XCOM Data Transport also disables future use of zIIP, and restart the transfer from the last checkpoint. On the restart, zIIP is not used due to the disabling of the support.
The output of the SHOW command for a specific transfer displays the current zIIP CPU eligibility and utilization times.
This section contains the following topics:
This section describes the new PARM and Configuration parameter value allowed by the CA XCOM Data Transport Server and XCOMJOB TYPE=EXECUTE jobs for enabling /disabling zIIP support.
Specify YES or NO (Y or N are also acceptable) to indicate if zIIP support is to be enabled for the Server or XCOMJOB TYPE=EXECUTE Job. The default is YES.
This section describes the new modify command to manage and monitor zIIP utilization by the Server.
Allows for management of zIIP services.
F XCOM,ZIIP[,{ STATUS | ENABLE | DISABLE}]
The following operands may be used with the ZIIP command:
Displays information pertaining to number and status of main CPU and zIIP processors.
Displays status of zIIP services for all CA XCOM Data Transport facilities that are zIIP aware.
Displays current statistics for the amount of processing time that was eligible to execute on zIIP and actually was executed on zIIP.
Will enable zIIP to be utilized for offloading processing from the main CPUs.
Will disable zIIP from being utilized to offload processing from the main CPUs.
Currently only the Compression and de-compression facilities of CA XCOM Data Transport support the offloading of processing to a zIIP.
The use of the command requires that the command issuer's security authorization contain the following access level and the security class specified by the OPERCMDS parameter in the configuration member:
XCOM.applsec.ZIIP.operand
XCOM.applsec.ZIIP.STATUS
XCOM.applsec.ZIIP.ENABLE
XCOM.applsec.ZIIP.DISABLE
The variables represent the following values:
applsec—the value of the APPLSEC parameter in the Default Options Table.
The History Record Detail screen provides information on the set of file transfers defined on the File Transfer Display Select screen. Additional statistical information will be presented to indicate CPU and zIIP processor utilization.
CA XCOM SEND FILE REQ.# 001302 QUEUED MONDAY AUG. 01, 2011 09:32:15
COMMAND INPUT ===>
Local System Identification Server: 1234XCOM Port: 8040 Protocol: TCP History System ID: XC12 History System Name: XCM123 Invoking Job: USER01 Sched. Start Time: MONDAY AUG. 01 2011 09:32:19 Transfer ID: USER01234 End Time: MONDAY AUG. 01 2011 09:32:19 Encoding : UTF-8 Last Action: * NOT USED* Status: COMPLETED Priority Sel: 016 Exec: 016 Compress Mode: RLE Trans. Time (Secs): 1 Compress Factr: 02.0 Transfrd. Records: 1 Bytes: 48 Bytes/Sec: 1 Compress Bytes: 49 CPU: Time: 216,789 zIIP: Elig: 47,635 (ms) TCB: 169,010 (ms) zIIP: 45,685 SRB: 47,779 CPU: 1,949 Charset Input Error : REPLACE Replace Count: 0 Charset Convert Error: REPLACE Replace Count: 0 Last Ms: XCOMM0137I 1 RECORDS SENT SUCCESSFULLY - FILE=XCOM.USERID01.MG ‑‑‑‑‑‑‑‑‑‑‑ S E N D I N G S Y S T E M I N F O R M A T I O N ‑‑‑‑‑‑‑‑‑‑-- System ID: *LOCAL* User ID: USER01 Notify ID: N/A Unit: Volume: File Type: FLAT FILE File Name: XCOM.USER01.MGTCENT.TXT Charset : CCSID#37/RE Rec Delim: EBCDIC:NA ‑‑‑‑‑‑‑‑‑‑‑ R E C E I V I N G S Y S T E M I N F O R M A T I O N ‑‑‑‑---- System ID: USER01-LAPTOP User ID: user01 Notify ID: user01 Unit: Volume: File Type: REPLACE File Name: c:\temp\mgtcent.txt Charset : CCSID#850/ML Rec Delim: EBCDIC:CRLF:NL F1=Help F2=SPLIT F3=End F4=RETURN F5=RFIND F6=RCHANGE F7=UP F8=DOWN F9=SWAP F10=Unicode F11=Hold F12=Alloc
The following fields have been added to this screen:
Specifies the job name that invoked the transfer.
Provide CPU utilization times for the file transfer. All times are reported in milliseconds (ms).
Time: Total CPU processing time for the transfer.
TCB: CPU processing time spent in TCB (task) mode.
SRB: CPU processing time spent in SRB (service) mode. This is the mode required to execute on a zIIP processor.
Provide zIIP utilization times for the file transfer. All times are reported in milliseconds (ms).
Elig: The amount of CPU time that was eligible to run on a zIIP.
zIIP: The amount of execution time on a zIIP.
CPU: The amount of eligible zIIP time that was executed on a normal CPU.
This section describes the new messages added to support zIIP utilization.
Reason:
The XCOM Server or XCOMJOB TYPE=EXECUTE has started and is providing an indication of the state of zIIP processing. The state will be either ENABLED or DISABLED.
Action:
None. This message is displayed for informational purposes only.
Reason:
The user entered a SHOW,req# command. This message displays as part of the response to the SHOW command. This message displays the actual and eligible amount of time that the transfer spent on a zIIP processor.
Action:
None
Reason:
Status of the CPUs for the LPAR is being provided, either as a result of the XCOM Server starting, XCOMJOB TYPE=EXECUTE or the ZIIP STATUS command. The message will display the number of standard and zIIP CPUs, along with the number of CPUs that are available.
Action:
None. This message is displayed for informational purposes only.
Reason:
The ZIIP STATUS command has failed to retrieve CPU status information. The API call to zIIP Enablement Services to retrieve CPU information has returned an error which is given as the return code. CA XCOM Data Transport will continue to operate, but will not attempt to move processing to a zIIP.
Action:
Keep the CA XCOM Data Transport log and SYSLOG and contact CA Technical Support.
Reason:
An attempt was made to initialize zIIP Enablement Services to allow for CA XCOM Data Transport to offload processing to a zIIP. The return and reason codes are from the zIIP Enablement Service API. CA XCOM Data Transport will continue to operate, but will not attempt to move processing to a zIIP.
Action:
Keep the CA XCOM Data Transport log and SYSLOG and contact CA Technical Support.
Reason:
An attempt was made to load the zIIP Enablement Service module, which is part of the CA Common Services library has failed. CA XCOM Data Transport will continue to operate, but will not attempt to move processing to a zIIP
Action:
If you are running r11 of CA Common Services, please insure APAR RO27636 is applied. For r12 of CA Common Services, please insure APAR RO27110 is applied. Releases of CA Common Services below r11 do not support zIIP Enablement Services.
Reason:
A process that was running on a zIIP has abended. The reason code is returned from the zIIP Enablement Service. zIIP processing is disabled, and the transfer will be restarted from the point of failure and will not use zIIP,
Action:
Keep the CA XCOM Data Transport log and SYSLOG and contact CA Technical Support.
Reason:
Issued as a result of the ZIIP command, status of each feature which can utilize zIIP processing is displayed.
Action:
None. This message is displayed for informational purposes only.
Reason:
Issued as a result of a ZIIP STATUS command, termination of the XCOM Server or termination of XCOMJOB TYPE=EXECUTE, provides statistical information as to the amount of processing time that was both eligible to be run on a zIIP and actually took place on a zIIP.
Action:
None. This message is displayed for informational purposes only.
| Copyright © 2012 CA. All rights reserved. |
|