ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Old records in u_fmsb50.dta causing issues
Article ID: 86807
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Affects Release version(s): 5
Error Message :
No error
Patch level detected:Dollar Universe 5.0
Product Version: Dollar.Universe 5.0.0
Description :Old records in u_fmsb50.dta file can cause some inconsistencies.
Example:
- Some launches terminated in time overrun, although the exepected conditionning launches terminated correctly.
- Launcher wakeup date in the past
Error Message :
No error
Patch level detected:Dollar Universe 5.0
Product Version: Dollar.Universe 5.0.0
Description :Old records in u_fmsb50.dta file can cause some inconsistencies.
Example:
- Some launches terminated in time overrun, although the exepected conditionning launches terminated correctly.
- Launcher wakeup date in the past
Cause
Cause type:
Configuration
Root Cause: It can occurs when some launches are reusing numproc of launches that had been already executed.
Configuration
Root Cause: It can occurs when some launches are reusing numproc of launches that had been already executed.
Environment
OS: All
OS Version: All
OS Version: All
Resolution
You can solve the issue using uxpursb command which is available for all Dollar Universe 5.x versions.
This command allows Launches older than a certain date to be purged.
The Company must be running to execute the command uxpursb (to access data) but the Engines corresponding to the target Area ( argument) must be stopped.
Syntax:
uxpursb
Where:
· : Dollar Universe Company. Format: 6 uppercase alphanumeric characters.
· : Dollar Universe Area. Format: 1 character, must be A or I or S or X.
· : Dollar Universe target node.
· : Target date after which the data will not be purged. This date should be provided in the format "YYYYMMDD".
Only the fact that the date contains 8 numbers is verified.
· : Optional. It can contain one of the 4 following values: LIST_NOALL, LIST_ALL, PURGE_NOALL, PURGE_ALL.
LIST_NOALL is used by default.
o LIST: List mode only. No Launch is purged.
o PURGE: Real purge mode. The purged Launches are listed. All production files are purged synchronously with the Launch base.
o NOALL means that records in the Launch base which are not also present in the job monitor nor in the execution history will not be purged, whatever their date.
o ALL means that these same data are purged on the date of their first Launch attempt.
Fix Status: Released
Fix Version(s):
Component: Application.Server
Version: Dollar.Universe 5.0.0
This command allows Launches older than a certain date to be purged.
The Company must be running to execute the command uxpursb (to access data) but the Engines corresponding to the target Area ( argument) must be stopped.
Syntax:
uxpursb
Where:
· : Dollar Universe Company. Format: 6 uppercase alphanumeric characters.
· : Dollar Universe Area. Format: 1 character, must be A or I or S or X.
· : Dollar Universe target node.
· : Target date after which the data will not be purged. This date should be provided in the format "YYYYMMDD".
Only the fact that the date contains 8 numbers is verified.
· : Optional. It can contain one of the 4 following values: LIST_NOALL, LIST_ALL, PURGE_NOALL, PURGE_ALL.
LIST_NOALL is used by default.
o LIST: List mode only. No Launch is purged.
o PURGE: Real purge mode. The purged Launches are listed. All production files are purged synchronously with the Launch base.
o NOALL means that records in the Launch base which are not also present in the job monitor nor in the execution history will not be purged, whatever their date.
o ALL means that these same data are purged on the date of their first Launch attempt.
Fix Status: Released
Fix Version(s):
Component: Application.Server
Version: Dollar.Universe 5.0.0
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
