|
IBM Unified Management Server v1.2
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2025 |
IZP3ALOC HAS INCORRECT SPECIFICATION FOR TARGET AND DISTRIBUTIONLIBRARIES | ||||
2025 |
ENHANCEMENTS, USABILITY UPDATES, AND BUG FIXES FOR THE IBM UNIFIED MANAGEMENT SERVER FOR Z/OS V1.2 | ||||
2025 |
IZPEXPIN INCORRECTLY FORMATS THE IZPD2DPM YAML FILE - VIA IZPSYNCY | ||||
2025 |
NORDIC CHARACTERS ARE INCORRECTLY DISPLAYED IN: EXPLORE -> STATUS ON UUISOR. | ||||
2025 |
SUPPORT GENERIC CLIENT CERTIFICATES TO REMOVE THE DEPENDENCY ON COM.ROCKETSOFT.ENABLEDEFAULTJAVACERTIFICATESENDING=TRUE IN UMS |
||||
2025 |
CHANGING UMS PARMLIB DOES NOT WORK IN ALL PLACES | ||||
2025 |
RUNNING IZPEXPIN CAN RESULT IN RECENT PARMLIB DATA LOSS | ||||
2025 |
THE UI LOGIC HAS BEEN UPDATED TO DISPLAY ALL RELATIONSHIP OBJECTS WITHIN THE HIERARCHY | ||||
2025 |
IZPGENER DOES NOT USE THE MEMBER NAME IN THE JOBS CREATED | ||||
2025 |
WHEN PROVISIONING AN INSTANCE USING UMS IN DB2 V13 FL100 SYSTEM THE JOB IS GENERATED WITH AN INVALID PARM (ACCEPT_FL = '100') | ||||
2025 |
DB2 OBJECT CHANGES ENCOUNTER FAILURES WHEN SAVING DDL CONTENTS VIA GIT | ||||
2025 |
IZPJT0001E - THE TEMPLATE 'JCL/DB2/TEMPLATES/PRODUCT/REGISTERSUBSYSTEM/01-REGISTERSUBSYSTEM/DEFAULT.JCL' DOES NOT EXIST | ||||
2025 |
IMS OBJECT DISCOVERY FAILS IF DBA USERID DOES NOT HAVE ACCESS TOA SYSTEM RDDS | ||||
2025 |
UMS TRIES TO READ ENCRYPTED CREDENTIALS, EVEN WHEN NOT CONFIGURED TO DO SO, RESULT IS AN ERROR WHEN OPENING REGISTRATION PAGE. |
||||
2025 |
APPLICATION REGISTRATION IS TAKING LONGER THAN EXPECTED. | ||||
2025 |
ADMINISTRATION TOOL INCORRECTLY DROPPING AND RECREATING ALIASES WHEN THE DDL ARE NOT SUBMITTED IN PROPER ORDER. | ||||
2025 |
SYNTAX ERROR IN CREATE/ALTER TABLE DDL OR CREATE TABLESPACE WITH KEY LABEL ATTRIBUTE. | ||||
2025 |
THE REGISTERED SUBSYSTEM LACKS ISTLS INFORMATION, RESULT IS A NULL POINTER EXCEPTION WHEN CREATING TUNING PROFILE AND QUERIES. |
||||
2025 |
ADD OPTION TO SUBMIT DB2 SUBSYSTEM REGISTRATION JCL AS THE LOGGED IN USER. | ||||
2025 |
INITIAL CONFIGURATION VALIDATOR CAN REPORT PROBLEMS WITH APIML, Z/OSMF, AND ZSS DUE TO NOT WAITING FOR SERVICES TO BE AVAILABLE |
||||
2025 |
THE REQUIRED OBJECTS LIST FOR A TABLE OBJECT ISN'T UPDATED IN THE INSTANCE YAML FILE WHEN THE TABLE IS MOVED TO ANOTHER DATABASE |
||||
2025 |
EXTRANEOUS AUTHORIZATION CHECKS AGAINST IZP.FUNCTION RESOURCES CAUSES ICH408I | ||||
2025 |
AN ERROR ENCOUNTERED WHEN ALTERING TEMPORAL TABLES | ||||
2025 |
"CONNECTION NAME NOT FOUND" ERROR IS THROWN IN UMS AS IDAA FAILED TO ESTABLISH A CONNECTION FOR THE SUBSYSTEM WHEN USING TLS | ||||
2024 |
UPLOADING A LARGE IIAS APPLIANCE MAINTENANCE FOR 7.5.12 USING UMS THROWS AN ERROR | ||||
2024 |
THE RESUME APPLY OBJECT CHANGES API CURRENTLY THROWS A NULL POINTER EXCEPTION AND RETURNS A 500 STATUS CODE. | ||||
2024 |
THIS APAR IMPROVES RUNNING COMMANDS BY BEING ABLE TO DISPLAY A COMMAND OUTPUT THAT CONTAINS LESS THAN CHARACTER. | ||||
2024 |
UMS FAILS IN FINDING IMS DATA SHARING GROUPS OR RETURNS MESSAGE IZPPL0092E IN IMS CONNECT DISCOVERY IF SYSPLEX NAME IS SHORTER |
||||
2024 |
ADDING AN OBJECT VIA DDL IN AN INSTANCE, THE REQUIRED OBJECTS SHOULD BE PRESENT. IF NOT, A NULLPOINTEREXCEPTION CAN HAPPEN. | ||||
2024 |
THE ABSENCE OF STORED PROCEDURE ADBGDDL CAUSES DROPS OF OTHER OBJECTS AND THE FREEING OF PACKAGES AND PLAN. | ||||
2024 |
ALLOWS NON-SUPER USERS TO SUCCESSFULLY RETRIEVE REGISTERED DB2 SUBSYSTEMS WHEN THE DB2 SUBSYSTEM DEFAULTPORT IS NULL. | ||||
2024 |
THIS APAR ALLOWS THE USE OF A HYPHEN CHARACTER, "-", WITHIN THE HOST FIELD WHEN CREATING A REPOSITORY DATABASE CONNECTION. | ||||
2024 |
IMS DATA SHARING GROUP REGISTRATION FAILS WHEN AN FDBR REGION EXISTS | ||||
2024 |
IZPSV0009E FAILED TO READ YAML FILE, RECEIVED ERROR: ARGUMENT TYPE MISMATCH. | ||||
2024 |
ENHANCEMENT, USABILITY AND BUG FIXES FOR IBM UNIFIED MANAGEMENT SERVER | ||||
2024 |
AFTER UPGRADING, GRANT AND REVOKE OPERATIONS ARE STILL BEING GENERATED EVEN WHEN THE "SUPPRESSGRANT" OPTION IS SELECTED. | ||||
2024 |
UMS CANNOT USE PORT RMI SERVER | ||||
2024 |
TABLE DDL PREVIOUSLY RESTRICTED CHANGES TO THE DB OR TS NAME, PREVENTING USERS FROM MOVING TABLES TO A NEW DB OR TS. | ||||
2024 |
UMS SUBSYSTEM UPDATE NOT AVAILABLE | ||||
2024 |
NULL REGISTRATION STATUS DURING DB2 SUBSYSTEM REGISTRATION, EVENTHOUGH JOB COMPLETED WITH RC4 | ||||
2024 |
DB2 DOE IMPORTS TABLES WITH LOB'S AND THAT USE IMPLICIT AUX TABLES INCORRECTLY | ||||
2024 |
UMS 1.2.0.8 - UPDATING THE FETCH OF OBJECT DETAILS FOR A DB2 SUBSYS WHEN THE DB2 SUBSYS IS NO LONGER A MEMBER OF THE DS GROUP | ||||
2024 |
THIS APAR ADDRESSES "FAILED TO LOAD MODULE DAJADMX" MESSAGES | ||||
2024 |
ENHANCEMENTS, USABILITY UPDATES, AND BUG FIXES | ||||
2024 |
MERGE BUTTON IS BEING DISABLED WHILE APPROVING THE PR REQUEST RAISED | ||||
2024 |
HANDLING A "$" (DOLLAR) CHARACTER WITHIN THE JOB LABEL OF THE JOB STATEMENT WHEN REGISTERING A DB2 SUBSYSTEM IN UMS 1.2.0.8 | ||||
2024 |
THIS APAR PROVIDES THE ABILITY TO HAVE A "DBAUSER" WHICH IS AUTHENTICATED VIA A CLIENT CERTIFICATE. | ||||
2024 |
UMS/DB2 ADMINISTRATION FOUNDATION, HEAVY ZIIP USAGE AND GLOBAL LOCKS FORMATION | ||||
2024 |
IMPROVED LOGGING, USABILITY UPDATES, AND BUG FIXES FOR THE IBM UNIFIED MANAGEMENT SERVER FOR ZOS V1.2 | ||||
2024 |
IZPPL0006E with 'Unrecognized field "STORAGESAVERPROBLEM"' when listing the tables of an accelerator in AF | ||||
2024 |
RUNTIMEDIR/UMS/OPT/BIN/IZP-CONCATENATE-PROCLIB.SH 132: FSUM7351 NOT FOUND | ||||
2024 |
DB2 ADMIN FOUNDATION INTERNAL ERROR DISPLAYING OBJECT STATUS INFORMATION | ||||
2024 |
UMS HIGH MEMORY USAGE | ||||
2024 |
UMS/DOE INSTANCE PROVISIONING FAILS WITH DATABASE NAMES CONTAINING A # | ||||
2024 |
ALIASES NOT CREATED IN UMS INSTANCE | ||||
2024 |
THIS APAR PROVIDES ENHANCEMENTS, USABILITY UPDATES, AND BUG FIXES FOR THE IBM UNIFIED MANAGEMENT SERVER FOR ZOS V1.2 | ||||
2024 |
THIS APAR WILL PROVIDE A FIX FOR SELECTING RI OBJECTS FOR A STORED PROCEDURE EXPERIENCE. | ||||
2024 |
THIS APAR ADDRESS AN ISSUE WHERE THE INCORRECT APPLCOMPAT VALUE IS USED DURING DB2 SUBSYSTEM REGISTRATION | ||||
2024 |
UMS SUPPORT FOR CONFIGURING PROFILEPREFIX WHEN USESAFONLY=TRUE | ||||
2024 |
IZPSYNCY FAILS WITH IZPPI0209E | ||||
2024 |
LIFT THE UMS 3MB YAML PARSING LIMIT | ||||
2024 |
UMS ISSUES HUNDREDS OF INFO MESSAGES PER SECOND WHEN CREATING AN APPLICATION | ||||
2024 |
THIS APAR PROVIDES SUPPORT FOR TLS 1.3 IN THE IBM UNIFIED MANAGEMENT SERVER FOR ZOS V1.2 | ||||
2024 |
UMS CAUSES ADDITIONAL LOGIN ATTEMPTS WHEN USING MFA | ||||
2024 |
IMPLICIT LOB/AUX TABLES WILL NOT BE INCLUDED ON APPLICATION DRY-RUN AND REGISTRATION. | ||||
2024 |
THIS APAR UPDATES THE LINKNAME OF A DB2SUBSYSTEM IF THE LINKNAMEIS NULL IN THE IBM UNIFIED MANAGEMENT SERVER FOR Z/OS V1.2 | ||||
2024 |
THIS APAR WILL PROVIDE A FIX TO OPTIMIZE THE PERFORMANCE IN UMS/DB DEVOPS EXPERIENCE. | ||||
2023 |
THIS APAR PROVIDES ENHANCEMENTS, USABILITY UPDATES, AND BUG FIXES FOR THE IBM UNIFIED MANAGEMENT SERVER FOR ZOS V1.2. | ||||
2023 |
THIS APAR WILL PROVIDE A FIX TO UMS PROCESS FLOW WHEN A USER DISCARDS CHANGES | ||||
2023 |
THIS APAR WILL PROVIDE A FIX TO THE ISSUES IN THE INSTANCE WHEN DATABASE AND SCHEMA MAPS SPECIFY MATCHING TO AND FROM NAMES. | ||||
2023 |
THIS APAR PROVIDES USABILITY UPDATES AND BUG FIXES FOR THE IBM UNIFIED MANAGEMENT SERVER FOR ZOS V1.2 | ||||
2023 |
THIS APAR PROVIDES USABILITY UPDATES AND BUG FIXES FOR THE IBM UNIFIED MANAGEMENT SERVER FOR ZOS V1.2 | ||||
2023 |
JUNE 2023 FIXES AND PRODUCT UPDATES | ||||
2023 |
JOBCARD INFO TRUNCATED, JOBPREFIX WILL NOW ACCEPT '@' | ||||
2023 |
THIS APAR PROVIDES ENHANCEMENTS, USABILITY UPDATES, AND BUG FIXES | ||||