DSXchange

Define what you mean by 'local variable' in this context. And detail for us what you intend to do with this as that could affect the answer given.

thanush9sep wrote:If I understood clearly, this should not be dstage but cmtapp user.

You did not understand clearly. And your script is working correctly assuming you want the O/S user rather than the logged in user/schema name.

OK, then it sounds like you'll need to pursue the course that Ray outlined. And yes, by 'traditional' I meant the 'Universe' repository we've always had and the RT_LOGnnnn dynamic hashed files. You can confirm by checking (off the top of my head) the setting of RTLogging / ORLogging in your environm...

dougcl wrote:

chulett wrote:You marked your post as using the UNIX system for your server, hence the confusion. ...

Actually I marked my post as using the UNIX system for our server, because we are. Raftsman is just here stirring up trouble

Sorry, failed to recognize the hijack!

Why not simply change the SQL to this?
You have no choice but to use custom sql for this, btw.

Have your SysAdmin do that for you.

I fail to see how any vendor can refuse to support their own product. Not something I would stand for.

Fair enough. Actually in thinking back about this and Ray's comment regarding the change, I think the change in behaviour is specific to datasets to make them act like their cousins, Scratch and Memory, seeing as how in earlier releases it all did not match up.

Or are noted, read the documentation. It's there for a reason.

That behaviour is specific to datasets, AFAIK.

Yes, a Sequence job can run both Server and Parallel jobs. No, there are no "settings" needed for this.

You marked your post as using the UNIX system for your server, hence the confusion.

Just like any other table, there's nothing magical about them... as long as 'access' means 'read', of course.

You would use a Server job and write a BASIC routine to leverage them.

Nope, got nothing to do with the "bit-ness" of the system.