DSXchange

The discrepancy is so large (71 against 6) that you've got to believe there's a bug in the buffering mechanism. Aileen, please report this through your support provider - it simply shouldn't work like this. That said, it was an interesting bit of detective work to eliminate all other possibilities.

This is weird. In your first post it was JOB_STG_Staff_Contact_C..ShrContSTGcurrentM.Trans_01.Lnk_Trans_01: dsintbuf_getrow() - row has 71 columns when 6 expected Later, it was JOB_STG_Staff_Contact_C..ShrContSTGcurrentM.SRT_01.Lnk_SRT_01: dsintbuf_getrow() - row has 66 columns when 6 expected This ...

If you use field mark (@FM) rather than comma, your data will magically be in multiple columns in the hashed file even though you only load the key and field #1. You can then read from the hashed file with a full set of column definitions.

Yes.

FieldStore() and Field() functions are a great way to implement what Ken has suggested, but make sure you understand them well. Use stage variables, then you can limit your output to happen only when a row is complete.

Ultimately the best solution for this kind of problem is table-driven, so that you can take into account public and business holidays - Mondays through Fridays that are not business days. You can readily implement this via a job sequence that is scheduled to run every day, prior to the first require...

There is only one reason that rows are rejected by a Sequential File stage in a parallel job: the data in the row does not match the metadata as specified for the output link in its schema. Create a rejects link and capture them by setting the rejected rows property to Output. This will allow you to...

40019 decodes (from the SYS.MESSAGE table) as "WRITE failure", which is not particularly helpful. It might be permissions (check at operating system level), it might be that the DS_JOBS table is corrupted (check using a query against it), it may be that its indexes need rebuilding (check with LIST.I...

System variable @PARTITION may do what you need. To be honest I'm not 100% clear on your requirement.

You should never need to abort jobs. Create jobs that never abort or generate warnings, control them through job sequences. Communicate to the job sequence via exit status (warnings will be genuine warnings), routines (for example row count from rejects link), files and/or jobs' user status areas.

Welcome aboard. :D Please post questions in the correct forum. (taken care of by moderator) Have somebody doing this kind of upgrade? Yes, lots. Search the forum. What about my current DS projects ? Do I need to rewrite all my DS projects ? No, they're automatically upgraded. Can I use some procedur...

Yeah, but that doesn't remove the text of each tag!

Ascential used to offer a training class called DataStage Essentials for Peoplesoft - you may ask whether that's still available.