Cumulative TQ Pubs Update and Usage Information
Table of Contents
PQ32632 and PQ32633
Note: APAR fixes in this section are updates to: . CS/2 PTFs UQ05603, UQ11442, UQ05604, UQ11443; . CS/6000 PTFs UQ05605, UQ11444, UQ05606, UQ11445; . CS for Windows NT PTF UQ22993. * PQ32632: TQ RMU Verify Function Needed For DAE Queues * PQ32633: TQ RMU Reset and Reorganize Function Needed For DAE Queues The following are updates to the DAE Communication System Technical Guide and Reference, Tables and Queues Management chapter. In the Utilities Section (final paragraph): The Resource Maintenance Utility is used to archive tables and queues, | restore previously archived tables and queues, reset, reorganize and | verify tables and queues. Using the Reorganize option, it also can be | used to move data from one table or queue to another table or queue, | respectively. In the Configuration Considerations section, under Start Parameters. | In order to enable optional start parameters with the menu-based | utilities, remember to set the "Use load parameters from ACB" flag. | Resource Maintenance Utility Start Parameters | --------------------------------------------- | | The Resource Maintenance Utility REM ACB, CS2SURC0.CS2NODE, can | contain the following start parameters. | | Trace option | | This start parameter allows a user to enable the Resource Maintenance | Utility trace feature. An example use of the trace feature is to | reveal details concerning a table or queue's integrity as determined | by the Verify or Reorganize functions. | | This parameter has the following format: | | TRACE=x | | where x specifies whether or not to enable trace. | | 0 Specifies the default of trace disabled. | 1 Enables trace. The file cs2surc0.trc is output. ************************************************************************ The help message "Action" sections have been revised to better explain table/queue recovery for help messages CSR1231 and CSR1232, as such: CSR1231: Corrupted free-record chain in file *** EXPLANATION: An internal Communications System error occurred while processing the request. A record requested from the free record chain is not found in the specified position. | ACTION: The table or queue involved is corrupt and should be recovered | from an archive copy. | | If a valid current archive exists (one which is not corrupt): | 1. Use the Online File Maintenance Utility to reset the corruptions. | 2. Use the Resource Maintenance Utility to Restore the table or queue. | | If a current archive does not exist, it may be possible to create one | from the corrupt table/queue: | 1. Use the Online File Maintenance Utility to reset the corruptions. | 2. Use the Resource Maintenance Utility to Archive the table or queue. | 3. Use the Resource Maintenance Utility to Reset and Reorganize | the table or queue. ------------------------------------------------------------------------ CSR1232: TQ corruption - Bad or missing file: *** EXPLANATION: An error occurred opening or accessing the requested table or queue resource. The principal and/or auxiliary image of the table or queue is corrupt. This can be caused by one of the following: * The table or queue was marked as corrupt prior to issuing the request. * The named file cannot be found in the location as configured. * A prior request to update the table or queue was interrupted during processing. * The maximum number of files that can be open at one time is exceeded. ACTION: Ensure the table or queue resource is defined correctly. Verify that the principal, and/or auxiliary image location fields are correct in the table and queues configuration. | The table or queue should be recovered from an archive copy. | | If a valid current archive exists (one which is not corrupt): | 1. Use the Online File Maintenance Utility to reset the corruptions. | 2. Use the Resource Maintenance Utility to Restore the table or queue. | | If a current archive does not exist, it may be possible to create one | from the corrupt table/queue: | 1. Use the Online File Maintenance Utility to reset the corruptions. | 2. Use the Resource Maintenance Utility to Archive the table or queue. | 3. Use the Resource Maintenance Utility to Reset and Reorganize | the table or queue. | To increase the maximum number of files that can be open at one time when the current maximum is too few, see the Distributed Application Environment Technical Guide and Reference.
PQ12298 and PQ14226
Note: APAR fixes in this section are updates to: . CS/2 PTFs UQ05603, UQ11442, UQ05604, UQ11443; . CS/6000 PTFs UQ05605, UQ11444, UQ05606, UQ11445. Note: These APARs were included in CS for Windows NT PTF UQ22993. The information in this section was included in the UQ22993.DOC readme contained in that PTF. * PQ12298: TQ Open/Close Performance Option * PQ14226: Confusion Over TQ OCPERF Requiring Enlarged Pools to Open Many T/Qs The following is an update to the DAE Communication System Technical Guide and Reference, Tables and Queues Management chapter, Start Parameters section. The parameters for REM priority class, REM priority delta, Maximum file handles and Memory file space remain as before. | In order to enable optional start parameters with the menu-based | utilities, remember to set the "Use load parameters from ACB" flag | when configuring the tables and queues REM ACB. Start Parameters ---------------- | TQ open/close performance option | | OCPERF=x | | where x specifies 0 or 1. | | 0 Disables TQ open/close performance (the default). | 1 Enables TQ open/close performance. | | TQ open/close performance option: | * Increases performance for applications which repeatedly issue | CS2_TQ_OPEN and CS2_TQ_CLOSE requests for the same set of tables | or queues. Performance improves most on platforms where the | tables and queues REM uses a multi-processed design, such as | CS/6000. Performance benefits may also apply to CS/2 and CS for | NT, but to a lesser extent. | | Performance improves only for iterative CS2_TQ_OPEN and | CS2_TQ_CLOSE requests for a table or queue, in situations where no | other application already has the table or queue open. There is | no effect on any other request, such as CS2_TQ_READ or | CS2_TQ_WRITE. | | * Alleviates timing and system load problems during closes and | reopens. | | If your applications open/close many tables or queues, the TQ | open/close performance option may require additional space allocated | in the work pool and control block pool.
PQ80220
Note: APAR fix in this section is an update to: . CS/2 PTFs UQ05603, UQ11442, UQ05604, UQ11443; . CS/6000 PTFs UQ05605, UQ11444, UQ05606, UQ11445; . CS for Windows NT PTF UQ22993. * PQ80220: Enhance T/Q REM To Handle File I/O Error 1. TQ REM to Support File I/O Retry on Error Note: This feature implemented on CS/6000 and CS for NT *only*. When TQ REM encounters a file I/O error while accessing a Table or Queue, the existent REM immediately flags that T/Q corrupt. Some customers report temporary periods where their disk may be inaccessible, with complete recovery occurring soon thereafter. This is believed to be the case with the SHARK file system, where Failover/Failback process occasionally causes a file to be temporarily inaccessible. TQ REM should provide an option for I/O retry on file access errors. TQ REM now provides a start parm, "FIOR" to enable File I/O Retry. (Implemented on CS/6000 and CS for NT only.) 2. TQ REM to log OS return codes on file I/O errors The following is an update to the DAE Communication System Technical Guide and Reference, Tables and Queues Management chapter, Start Parameters section. The existent parameters for the REM remain as before. | In order to enable optional start parameters with the menu-based | utilities, remember to set the "Use load parameters from ACB" flag | when configuring the tables and queues REM ACB. Start Parameters ---------------- | TQ File I/O Retry option | | FIOR=x | | where x specifies: | | The maximum number of retries the TQ REM attempts after encountering | a file I/O error while accessing a table or queue. Retries are | attempted at one second intervals until file I/O succeeds or the | maximum is reached. If the maximum successive retries fail, the | table or queue image is flagged corrupt. | | If FIOR is not specified, the value defaults to 0. | | Note: | When FIOR is specified, a delay results after a TQ file I/O error | occurs, continuing throughout the retry period. This delay | affects *all* TQ requests for the same API (for example, | CS2_TQ_READ) to all Table/Queues served by the same TQ REM.
PQ94891
Note: APAR fix in this section is an update to: . CS/2 PTFs UQ05603, UQ11442, UQ05604, UQ11443; . CS/6000 PTFs UQ05605, UQ11444, UQ05606, UQ11445; . CS for Windows NT PTF UQ22993. * PQ94891: TQ Open Maximum Option Needed The following is an update to the DAE Communication System Technical Guide and Reference, Tables and Queues Management chapter, Start Parameters section. All previously-existent parameters remain the same. | In order to enable optional start parameters with the | menu-based utilities, remember to set the "Use load parameters | from ACB" flag when configuring the tables and queues REM ACB. Start Parameters ---------------- | TQ Open Maximum option | | TQOM=x | | where x >= 0 | | 0 Sets TQ Open Maximum option to infinity (the default). | >= 1 Specifies the maximum number of Opens of each T/Q | Resource allowed for each Application Resource. | | The TQ Open Maximum option can be used to prevent applications | from leaking TQ Opens (TQIDs). | | Configure TQOM larger than the maximum number of TQ Opens which | each Application Resource normally requires for each T/Q | Resource. The TQ Open Maximum supports environments where | correct applications hold a reasonable number of multiple opens | for the same T/Q, while other applications leak TQ Opens. If | an Application Resource attempts more than the maximum number | of TQ Opens for a single T/Q Resource, the TQ REM automatically | closes the oldest TQ Open the Application Resource holds for | the same T/Q resource. TQ REM then opens the T/Q Resource as | usual, and returns a new TQID. | | Should the TQ REM encounter TQ Open Maximum exceeded, it | logs a single error message, "CSR603: Error - TQ Opens leaking. | Starting auto-close in TQ REM." The Application Resource and T/Q | Resource Names are identified as originator and destination of | the logged message. | | Note: The OCPERF and TQOM options do not affect TQ API requests | issued by DAE system REMs. DAE system REMs use | Application Resource Names prefixed by "CS2".
Last modified: October 6, 2004
DAE File Repository | DAE | Email DAE
 |
| About IBM | Privacy | Terms of use | Contact |