...
Backlog ID | Title | Description | |||||
|---|---|---|---|---|---|---|---|
| B-11537 | z/OS UAGSRV: Extend file monitor support for secondary agents in a sysplex environment | is sprint 12 not sure it will get completed | |||||
| B-11540 | z/OS UAGSRV: Support exits issuing messages to UAG JESMSGLG, LOG and TRACE datasets | The $LOGMSG macro will allow assembler programs to issue message to the UAG LOG dataset with a severity level of INFO, DEBUG and TRACE. The appropriate log level will need to be set to allow the messages to be logged. It will allow TRACE messages with a level of ENTRY, EXIT, TRACE and WATCH. Trace will need to be active to allow the messages to be logged. For JESMSGLG messages, the message number will be 1097. The levels will be ERROR, WARN, INFO, AUDIT and TRACE. The appropriate log level will need to be set. The macro specification will allow a single text string to be sent. The assembler code line number and the issuing CSECT name will be sent as well. These will be printed in the LOG and TRACE datasets to indicate the source of the message. | |||||
| B-11561 | z/OS UAGSRV: Implementation bi-directional messaging between primary and secondary agents in sysplex | With Universal Agent 6.9.0.0, UAG for z/OS will create and join a Sysplex group if it is running Sysplex-aware. The XCF group name will consist of the characters UAG, followed by the first 4 (upper cased) characters of the system ID (system_id from UBRCFG00). Each UAG will have a member name, which will be the group name appended with @ and followed by the MVS system name. So, for example, my UAG with a system ID of mndv, running on DVZOS202, would have a group name of UAGMNDV and a member name of UAGMNDV@DVZOS202. | |||||
| B-06132 | Recognize when a pre-allocated file is updated on z/OS (Implementation)
| Currently, UAG for z/OS uses SMF record type 15 to detect dataset creates. The same record can be used to detect updates. Create File Monitors will be modified to trigger only on creation of a dataset. Change File Monitors will be supported by having them trigger on dataset updates. Additionally, UAG for z/OS will start collecting SMF type 18 records. (These are created when a dataset is renamed.) When a dataset rename is detected which matches a Change File Monitor, the File Monitor will also trigger. For Change File Monitors, z/OS will support only the “Monitor File(s)” field in the “Agent File Monitor Details” section of the “Agent File Monitor” pane. Wildcards * and ? will be supported. For Create File Monitors, z/OS will continue to support only the “Monitor File(s)” field in the “Agent File Monitor Details” section of the “Agent File Monitor” pane. Wildcards * and ? are supported. Both Create and Change File Monitors will not be triggered until a dataset has been opened for output and then subsequently closed. Change File Monitors will also trigger when a rename of a dataset completes successfully. | |||||
| B-10813 | Suppress ICH408I message for unprivileged z/OS Agent install | Running UDM with an un-authorized User message ICH408I USER(UBRTRP ) GROUP(UBRGRP ) NAME(####################) is shown within the LOG. Even though it is an informational message confirming that the user does not have authorization, it is often considered as a "security issue" in Audits. To avoid confusion, the RACF-check, leading to thai message, will be ommited when an unauthorized user is used. |
...