DSXchange

No need for an additional stage if it's already available in the User Status area of one of the jobs in the Sequence job. Besides, that wasn't the question. Juls asked about accessing it from two sub-sequence jobs called from a third top level sequence job. The User Variables stage won't help here. ...

One big problem with this approach - jobs have a 'User Status' area, routines don't. Besides, if you've already got a delimited string of all the values, do you really need to go to all that effort to park it in User Status? Put it in a User Variables stage instead... assuming you have 7.5.x install...

Can I have a sequencer above the job which passes 'ABC','XYZ'.....to filename and runs the job 4 ( the no of files I have) times. and loads table. Short answer is 'yes'. How you architect that is another matter. Do you know the four values ahead of time or do they change from run to run? If they ar...

Since you've never posted your job design, this 'problem' is a little hard to follow. However, it sounds like you are trying to generate this psuedo 'key' before the aggregator stage and it comes out of there jumbled up. If that's the case, then the answer is simple - assign it after the aggregation...

3) in the sequence job I call another routine that I wrote that extracts the user status. This part shouldn't have been necessary. You should have been able to use StageName.$UserStatus directly. Now a new question.... can I persist that same user status value in between 2 sequence jobs that are ca...

I was wondering if that was the case. Yes, you'll need to pass back a delimited list of the values to be assigned and have the downstream job pick them up. If you are on a recent version, the actual parsing can be done right in the parameter assignment field.

Do you have a link back to the original post?

It inherits the default value from whatever job the SC is included in.

A routine that does not return a zero is considered to have failed when you let the Sequence job handle 'errors' automatically. Read the online help for that option to see how to handle the situation.

Where/how are you actually using this routine? You'd need to run the job after setting the parameters... once you release the handle, the settings will be lost.

No problem. Keep in mind the fact that, until someone replies, you can delete the last post in a thread if it is yours. Now that we've both replied since then, you are stuck with them.

There's also the conversion code MB you can use with Oconv.

True. And only somewhat in the 7.1.x release. That would be why it's best to have a 7.5.x version to do this.

CFF or Complex Flat File stage... assuming .CPP is some sort of copybook type file holding a COBOL FD.

Searching for the 'PWD thingy' message in the forum turns up someone with the same problems. See if their solution helps.