Issue

Issue Type
Design
Configuration

Unable to send mail using mailx command

Resolution
Verify the TNS entry:
Ensure the tnsnames.ora file has the
connection details for the DB you are
trying to connect to. If it does not, request
the engineering team to update the
tnsnames.ora file
Configuration
Add the From address using -r option
mailx -r <from address>. Check the "Send
the email from Datastage" section in this
document https://dept.sp.ford.com/sites/ACE/DStag
e/ds85migration/Shared%20Documents/D
ataStage%208.5%20Application%20QA%
20and%20Prod%20Setup%20Process%2
02013-04-04.pdf to understand how to
register and know more about adding
from address to the dssendmail_template
file.
Design

Unable to send mail using Notification Activity

Check the sendmail command in the

dssendmail_template.txt file. Ensure it
has -f parameter. If it does not have,
follow-up with the engineering team to fix
8.5 requires the from address specified
unlike the lower version. Check the
"Send the email from Datastage" section
in this document https://dept.sp.ford.com/sites/ACE/DStag
e/ds85migration/Shared%20Documents/
DataStage%208.5%20Application%20QA
%20and%20Prod%20Setup%20Process
%202013-04-04.pdf to understand how to
register and know more about adding
from address to the dssendmail_template
file.
Configuration

Oracle Stage - Unable to connect to Database

Engeering team
Support Required ?

Unable to open the jobs. Receive the following

error
'\Jobs\TVM\TVME\SECOND_NEW': The string was not
recognized as a valid
DateTime. There is an unknown word starting at index 0
Record Dropped warning in a lookup stage

Follow-up with the Datastage Engineering

team
to have the patch
"patch_JR42384_client_windows_8502"
installed.
Configuration
Ensure that the metadata matches with
datatype and length for all the columns.
Design

An after job routine warning as below:

TPUBGENERJ004EXA_Db2dt3.12384.AfterJob
(DoJobReport): Failed to open directory
/ford/proj/IBM/alldsmetrics/PPUB_DEV_proj

Follow-up with the Datastage Engineering

team to add the project directory under
alldsmetrics directory
Configuration

Stage,0: Warning: At row #, link "Link Name",

while processing column "Column Name"
Value "VALUE" truncated to "VALUE"
Error writing to RT_CONFIG144
Error calling subroutine: DSR_EXECJOB (Action=30)
check Datastage is setup corrently
unable to write record <JobName> to file RT_CONFIG142
<StageName>: File tera_cs.txt either does not exist or
contains no values for ICU charset 'ISO_8859-1:1987';
ISO-8859-1(ASCII)for network attached and EBCDIC for
Channel attached is used instead

Check if the extended attribute for the

column is set to unicode. If yes, remove
that. Set the extended attribute to unicode
only if the column has unicode data
The project directory needs to point to
project group
The project directory needs to point to
project group
The project directory needs to point to
project group

Y
N

Design

Configuration

Configuration

Configuration

<StageName>: Warning: <JobName>: The size specified for

column '<ColumnName>' (1) is less than that of the source
table column (4);data truncation may result.

Mapping to inappropriate NLS Map name

could cause this issue. Check this out
with the Engineering team
Configuration
Ensure the data types for a column in
both the links are consistent. If a
difference is required, handle that with a
modify explicitly.
Design

There is a truncation issue with DB2 enterprise stage while

handling foreign language data, especially when there is
data with an "accent". For example, a 140 character data
is read as 143 or more depending on the number of accented
characters.

In data using foreign language,

a character with an "accent" appears
to be taking up extra characters.
If a DB2 legacy stage is used, replace it
with DB2 connector stage

Design

PIVT,0: Invalid date value in setOutputFieldAsDate()

for field '1' in output dataset '0' Date cannot be later
than 9999-12-31 or earlier than 0001-01-03 Julian days
value = 1721424.

Implicit conversion from source type "ustring[3]" to

result type "string[3]": Converting ustring to string
using codepage ISO_8859-1:1987

PIVOT stages within Datastage 8.5

seem unable to handle dates 0001-01-01
or older. Use date 0001-01-03 in such
instances temporarily until a permanent
solution is found.
Design
Truncation issue when the extended
attribute between links do not match.
If the data is unicode, ensure that it is set
to unicode in both the links in order to not
be truncated
Design