DSXchange

Ken stole my thunder :D That was going to be my answer if your difficulties were in splitting the data into discrete files and not in generating the other information.

Kevin,

is the control, header and footer information a function of the data, i.e. can you change your processing to have one job create {n} files of 998 or less records without a header/control/footer and then a second process to add this missing information?

Creating files doesn't get cached in DataStage. Is your "S" drive on the network? Can you try a test job with all the file to a local drive?

I've never encountered that error before, but have created many hashed files simultaneously. I wonder if the error might be due to Windows drives. Is the "S" drive local to the DataStage server or on a mapped network drive? Could you test the hashed file creation on a local drive to see if the error...

Jeremy, the DSSetJobLimit() is set when coding a call to DSRunJob() . You have specified a PX job but the Server forum - unfortunately the limit function only applies to DataStage Server jobs and not to PX jobs, I don't know if that applies to your situation. The "Job Activity" object does not allow...

The DSGetStageInfo() call will only give you the stage variable names but not the formula/derivations thereof. This metadata is not exposed via any of the APIs. The values are stored in the DS_JOBOBJECTS table but are not meant to be accessed.

Convert the numeric values to VarChar then do a trim to remove leading 0's and then perform your concatenation. Look up the trim() function declaration in the PX manual, I think it is trim(In.Column,"0","F") but I'm not certain and don't have access to the manual here.

I was looking at the issue from a server job perspective, not PX. I'll take a look later at the same copy book declarations in a PX job and see if I get different results on my system.

Welcome to DSXchange, Sylvan.
Could you tell us what the data is that comes in and what you want output? The conversion looks a bit too complicated.

I am fairly certain that this is a usage issue and not a limitation, I've used quite complex copybooks with all sorts of groupings and levels. Could you state your exact error message - are you using the S1-KEY as a column or the single components? If you are populating the components what happens w...

Remove the S1-KEY from the copybook, or change it to a level 02. I'm surprised that the import isn't working correctly, but I'm not at a terminal where I can test this out.

The DSLogInfo() is a routine and not a function and does not return a value. This will neither compile nor run.

Why don't you just pass the string variable $summary as a parameter to your fmail instead of the current DSLOG?

You need to convert the displayable char input string into the appropriate format, or perhaps let DS do it for you implicitly. Are you looking at a timestamp or a date field or a DB/2 Time? With a time format, what are you writing to (ODBC, DB/2, sequential file)?

Emma,

your COBOL copybook is invalid without PIC clauses for each data element, without a PICture definition the cobol copybook declares no data, just groupings.

No.

I had to look up "NACHA ACH" on google before I knew the answer. "NACHA" -> Electronic Payments Association and "ACH" -> Automated Clearing House.