A fix is available
APAR status
Closed as program error.
Error description
PROBLEM DEFINITION: Experiencing extremely frequent VST corruption due to wrong disk prefix in the TSAM environment. This is happening several times a day, requiring to manually run a query to identify the corrupted VSTs and manually fix the corrupted VST to avoid provisioning failures, which is an unsustainable scenario. STEPS TO REPRODUCE: run a provisioning request (create project with VMWare servers) and get error 'CTJZI1717E Insufficient resources available to satisfy request'. CURRENT ERRONEOUS RESULTS: provisioning fails unless corrupted VST(s) are manually identified via query provided by L3 and manually corrected. EXPECTED RESULTS: provisioning succeeds without corruption of VST ENVIRONMENT: ISDM 724 for X
Local fix
N/A
Problem summary
When submitting a provisioning request, the request fails prior to any workflow being started with the error "CTJZI1528E - Insufficient resources available for project on dates requested"
Problem conclusion
You may experience this problem if you are running any TSAM version from TSAM 7.2.4.0 through TSAM 7.2.4.4. APAR IV55407 has been created to address this issue. The permanent fix for this problem is scheduled to be included in TSAM 7.2.4.5, and official LA fixes are being provided for TSAM 7.2.4.0 through TSAM 7.2.4.4. However, in order to confirm you are facing this exact issue, when you see the error "CTJZI1528E - Insufficient resources available for project on dates requested", please run the following sql: select vst.server_template_id, rr.resource_type_id, rr.group_name from resource_requirement rr,tpvirtualservertemplate vst where vst.server_template_id = rr.server_template_id and vst.name like 'ODSDS%' and rr.resource_type_id = 2 and rr.group_name not like 'vSCSI-%' If the output contains one or more rows, please follow the below directions for each row in the output in order to fix the problem: Navigate to the respective virtual server template (VST) by searching for the server_template_id value in the above sql output using the DCM Object Finder in the Maximo Start center page. Then proceed to correct the disk resource group name using the following steps: - replace in the field "Resource Group" the prefix "vm-fs-" with "vSCSI-" (keep the rest of the name) - verify that "Virtualization Type", located at the upper part of the window, is set. If not, set it to the one that best fits the hypervisor used (e.g. VMware ESX, LPAR, KVM, etc) - save the virtual server template Once you have corrected all virtual server templates per the output of the sql specified above, you may repeat the provisioning request, which should now complete successfully.
Temporary fix
Comments
APAR Information
APAR number
IV55407
Reported component name
TSAM (& INSTALL
Reported component ID
5724W7800
Reported release
724
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-02-13
Closed date
2014-03-06
Last modified date
2014-03-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TSAM (& INSTALL
Fixed component ID
5724W7800
Applicable component levels
R724 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFG5E","label":"IBM Tivoli Service Automation Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"724"}]
Document Information
Modified date:
03 October 2021