METASTAGE_LOC_INFO in CAHETLCPCA type *FILE not found

Error message (From Datastage Level)
FPCONDTL,0: Fatal Error: Fatal: [IBM][CLI Driver][AS] SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code "CCAREPDATA.FPCONDTL". SQLSTATE=57033
DSTAGE-DB2CLI-0026`:`SQLFetch: Error retrieving results from server.

Error message (From AS/400 Level)
Target job assigned to handle DDM connection started by source system over
TCP/IP.
Local relational database accessed by LTOH0010ISPHN01.
METASTAGE_LOC_INFO in CAHETLCPCA type *FILE not found.
Prepared statement STMT0005 not found.

Cause:
This problem happened when there is job trying to access a table and some parallel insert / updated is being processed into the same table. So, in this case there is a SHARED lock applied for that particular record which is under transaction, as it was not in committed mode.

Resolution:
In the stage level, there is an option to set the Isolation level, which can be changed from Cursor Stability > Read Uncommitted. Setting this condition, we can also fetch the records which are not in the committed mode ignoring the SHARED lock processed by the record level information.

PT_Decimal::operator=: the source decimal has even precision, but non-zero in the leading nybble, or is too large for the destination decimal

Error Message:
APT_CombinedOperatorController,0: APT_Decimal::operator=: the source decimal has even precision, but non-zero in the leading nybble, or is too large for the destination decimal.

Resolution:
The error message is not quite informative as far as the datastage logs are concerned. So,

set APT_CHECK_DECIMAL_VALIDITY=1 in the project level.
Once you rerun the job you will see some kind of different log message like
APT_CombinedOperatorController,0: Fatal Error: APT_Decimal::assignFrom: the source decimal (precision = 38, scale = 10) is too large
for the destination decimal (precision = 3, scale = 0).

Now, looking to this log, you can make decision, which target field with length Decimal (3,0) being mapped from Integer (Default precision is 38:10) when it is mapped. Then you can go back to your job and modify the job accordingly.

Some other points (For Numeric / Decimal):
The following table specifies the storage size required based on the precision specified for the NUMERIC or DECIMAL data type:

Precision Storage Size
1 - 9 5 bytes
10- 19 9 bytes
20-28 13 bytes
29-38 17 bytes

ISv8.1 - installation of IA8.1.1 - how to keep silent

Question:
Trying to automate the client upgrade of Information Analyzer from v8.1 to v8.1.1 (installation of IA-811-upgrade-V2-windows.ispkg)

- is there a way to avoid the need to enter '1' and 'enter' to accept the license agreement during console-installation?

In the main installations a response file can be used, but is there a way for updates?

My installation command:

C:\IBM\InformationServer\ASBNode\apps\jre\bin\java.exe -jar updater.jar -i C:\IBM\InformationServer -p C:\patch\81-critical-patch.ispkg -console

Answer:
InstallPatches.sh:
"\IBM\InformationServer\ASBNode\apps\jre\bin\java" -jar updater.jar -i "/IBM/InformationServer" "$@"

TestInstall.sh
./InstallUpdate.sh -version -console
./InstallUpdate.sh -p IA-811-upgrade-V2-windows.ispkg -console -force << EOF
1
EOF
./InstallUpdate.sh -version -console

Lost DataStage Designer menu

For several designer questions on the techlist, especially dealing with windows that show up off screen due to resolution / duel monitor changes, it has been recommended to delete the registry keys under HKEY_CURRENT_USER\Software\Ascential Software\DSDesign to reset the Designer Window positions. So you may want to backup that registry key, and then clear it out. I believe one of the DSDesign-Bar? entries under it is the position of the Menu, but I couldn't tell which one. If something bad happens, you should be able to restore your backup of the registry key.

I deleted the key on my desktop, after docking the menu tool bar on the bottom of the screen. The registry key was recreated the first time I started the designer client, and my menu tool bar was back at the top as normal. So this would be my first step in solving.

Can't view datatype from the Datastage designer.

Cannot find parameter file record DSMFParams in &UFD&

This problem happened when the DSMFParams file missing from the "$DSHOME/../Projects/" folder.

Resolution: Checked that DSMFParams file is changed to DSMFParam.old. The DSMFParams.old file is renamed to DSMFParams. You need to open a new designer session to overcome this issue.