DSXchange

How could I query DataStage's UniVerse to extract job schedule info, such as:
Your help is very much appreciated!

Determine what the format is; if correct, write it as is otherwise use the famous oconv and iconv functions to re-format the date. Something like this for your derivation: if InputRec.DateIn matches "2N-3A-4N" then oconv(iconv(InputRec.DateIn, "D-DMY"), "D-DMY[2,2,4]") ...

Welcome to DSXchange! :D (I should be saying that to myself, for not posting anything for so long.)

Which Windows OS are you running? Which service packs are installed?

Can you view the properties when you create a new job/sequence?

I know it's possible to create a new category, move jobs from the old to the new category and then delete the old category, but is it possible to rename a category without doing the above?

At last I got a bit of time to spend on this again. It turned out that the definitions supplied are indeed slightly off from the actual data: X72002-CO-ID PIC XX. X72002-ACCOUNT-NO PIC S9(15) COMP-3. X72002-PRDCT-CD PIC X(03). X72002-SUB-PRODUCT PIC X(02). X72002-CUST-NO PIC 9(15). X72002-PRIMARY-OF...

You can use a where field_name = ? clause in user-defined SQL the same way as DataStage does with a generated SQL query. Then, hook up a field to it via the GUI designer in your transformer.

From my guesswork it looks like it could be: 0Ah - 0Ch (bytes 11 - 13): PRDCT-CD ("DDA") 0Dh - 0Eh (bytes 14 - 15): SUB-PRODUCT (null value) 0Fh - 1Dh (bytes 16 - 30): CUST-NO ("000000000124507") 1Eh - 22h (bytes 31 - 35): PRIMARY-OFFICER (spaces?) The rest is gobbledeygook again...

I am suspecting that the definition doesn't match the data but don't want to jump to conclusions with my limited mainframe file knowledge.

Apologies again, I forgot about the COMP-3 packing, so the string mentioned earlier won't necessarily be ACCOUNT-NO, right? The next 15-digit number that's not COMP-3'd is CUST-NO.

So, considering the COMP-3 packing, "DDA" could very well be PRDCT-CD.

Apologies, "DDA" must be something else- it's too early in the record. The string "000000000124507" must be ACCOUNT-NO though, since it's 15 bytes long.

00 0F 00 00 consistently occurs at the start of each new record...

Welcome to DSXchange! :D

Searching can be a useful way to find information relevant to the situation you are dealing with. A search could yield results such as this topic and this topic that may provide the answers you are looking for.

I have a mainframe file that's been FTP'd to the DataStage server and this data has to go out into a normal Unix flat file. I haven't worked with an EBCDIC mainframe file in DataStage before, and it shows, so I could do with some help please. I don't have access to the CFD but the file definition ha...

Very good Ray, very good! So how does one get to this subroutine in RT_BP415-yah-dee-yah-dee-yah and check it out, and how does one find out which file? Is it necessarily a hashed file?

Hi Mark, long time no see!

Sounds awfully much like a hardware device failure. Bad sectors, perhaps?

A thousand apologies, effendi. *** LAME JOKE ALERT *** That's what happens when trying to scan through threads very quickly when hyper-threading is not enabled.