DSXchange

You should pull out the jobs you do not need and just use the ones you do need. There are lots of jobs that are just to show you how to create metadata from system tables or from the DataStage repository. EtlStats has several jobs which are not used to get row counts. The same is true for the routin...

Please edit your post and put code tags around it so we can see the indentation.

It looks like at first glace you only read one line from the sequential file.

I would use spaces() or str(). Should do what replicate used to do.

Try Ken's way. It should fix this error.

This job is not a recommended practice. This job would loop through all jobs and clear file on RT_LOGnnn.

You should setup logs to autopurge.

There is an audit table only it is hidden. Version Control will track versions of jobs if used. Automated exports can also satisfy the tracking of changes. I have never tried logging in with an expired password. I am sure there could be an admin solution to satisfy this need. Maybe a shell script to...

It is case sensitive. DSJOBNAME is not the same as DSJobName.

Just use the macro instead of any parameter.

Did that work?

You don't need the parameter JobName.

That is true. If you do not use a path or an account in the hashed file stage then it goes into the project directory. Therefore if the project was on the new drive then the hashed files would be okay. My suggestion was for the existing projects to start using the new drive so the old drive does not...

You can put new projects on this drive if it is a local drive and not a networked shared drive. DataStage may complain about a shred drive. You need to put hashed files and sequential files in path on this drive so save disk space. This should be done using parameters like pHashedFilePath and pSeqFi...

Just in case this is confusing for people. The uv command sets the ulimit and then runs uvsh. uvsh and dssh are the same command on DataStage. This is called the Universe shell or the DataStage engine shell. The Universe shell is the command line interface to the Universe database in a similar manor...

Post the routine code.

DSJobName is a macro. I doubt if it will work with # around it or buried in text. Try it by itself. It should work.