DSXchange

Got it; and I should have caught that link on your sig line, will use it for sure!

TIA,

ff

Thanks Franklin, that did the trick. COBOL table importer IS a little finicky! You didn't work in Los Gatos back in 04' for the Ascential COBOL support team did ya? have a G'Day!

ff

Greetings, Having a problem importing a COBOL CopyBook as a COBOL FD table def into DSEE via the designer. I get the following error: 'PIC' PICTURE character string format must have at least a 9, A, G, N, or X symbol. In trying to import the following 2 lines in the copybook: 000364 15 ML-CON-LOT-RL...

Turned out we had the wrong copybook, topic closed.

Thanks Franklin, let me chase down the CFD, will also take your alternate table def comments into account. Be Back.

Greetings, I've been saddled with a group of DataStage EE and Server jobs that are suffering of the same aliment; seeing special or non-printable characters in various fields in the source records, and can't find a way to eradicate them once in DataStage. I've read the various posts in this forum on...

Problem solved. Turns out the name/value pair I had entered for the custom authentication header, was incorrect based on my interpretation of it. Once I fixed that, we were good. As for the Base64 encoding requirement on the creds, not sure how that was satisfied under the covers as I was using a UT...

Greetings, Trying to call a RESTful web service doing s GET http method in a hierarchical stage; nothing fancy, no request input expected, and response is a text string that returns a status code. Have specified the required authentication header provided, however the username:password pair authenti...

Sorry for the late response guys, been drinking from the fire hose lately.. Craig, you were kinda right, once I got a better understanding of the data it all boiled down to: "stick a 20 on the front of it or a 19 to indicate the 20th or 21st century, then just slide a couple of dashes into it.&...

Got it and makes sense, Thanks guys!

IHAC who would like to know why Oracle database NUMBER type that used to import into DataStage via the Oracle OCI Stage as Decimal 38, now come in as DOUBLE via the Oracle Connector.. Any takers?

TIA,

ff

Thanks Guys,

The outbound column should be a timestamp. Thus far I have converted the incoming decimal to a string, will now execute steps 2 and 3.

Greetings, I have an incoming mainframe date which thus far I have converted from a decimal to a string, which comes in the format CYYMMDD ('C' for century, 1 or 0) and I need to convert it to DD-MMM-YY:00:00:00. Any ideas how I can do this in a derivation? I figured I'd start by trimming off the le...

Got to the bottom of this; for whatever reason although the columns and datatypes all lined up with the table in the database, once I imported a fresh table def from the database itself into DataStage and pulled that into my Oracle connector, problem went away! Gotta love those DSEE red herring mess...

Greetings, Have not seen this one before; imported a table def into an Oracle connector and pushing the output to a peek stage for starters and to eliminate any other logic issues. The job compiles fine but when I go to run it the job aborts and in the log file I find an informational message saying...