DSXchange

You could if you used a Reference Lookup to retrieve it first. Not saying that's a good way, but it is a way.

Based on what you posted - three EReplace functions, one after the other. Simple as that.

Should be simple enough to double-check, but I'm not sure if you can have a 'dot' in the Invocation ID.

Ok... give an example of a packed field on the mainframe - something like S9(9)V99 COMP-3 let's say - and your corresponding column definition in the FTP stage.

You can do it either way. I'd probably go the routine route so that the rules are documented in one place and it can be leveraged in many. It will also makes changes easier as the jobs that reference it wouldn't (necessarily) need to change when the rules changed.

You know what is not recommended and you are working to get rid of? And hashed files over 2GB are perfectly fine as long as they are 64BIT hashed files. 2000 or 2050 sounds a bit high to me... not sure if that would also cause an issue. We are supporting something like 15 projects with our T30FILE p...

More wondering how are you defining the metadata for the packed fields?

Hmmm... I can't think of anything off the top of my head that I've had to 'work around'. And I believe that 'too many subdirectories' issue is specific to the AIX operating system. Not much you can do there other than live with that limitation. The OP may be running into resource issues. I'm curiou...

What is the nature of the strange problem? How are you defining this packed data and what issues are you having with it?

I don't think it's possible to answer your question without seeing the actual job and what you are doing in it. As in posting a dsx export of it somewhere.

BTW, you hit the nail on the head, we are always creating almost each hash file again and again every day. Stop. While the norm is to rebuild the contents of hashed files run to run, there usually isn't an overwhelming need to delete and recreate them each run as well. Why not switch to simply clea...

The error is on the output file.

Otherwise, check that it is a valid path and you have permissions to write to it. Or if the file already exists, that you have permission to overwrite it.

Unfortunately the affected hash file in the unix directory does not look like a normal one. There separate files per each record, where the name is the key of the hash file. I forget what silly type this is but it is one of the ways that a dynamic hashed file can 'corrupt' itself, especially if you...

Have you done much with stage variables? That would be the typical way to compare anything across adjacent rows - assuming the incoming data in sorted correctly. You would setup two, one to compare the current value with the previous value and a second to reset the current value. This leverages the ...