DSXchange

It's the dreaded Field Marks (@FM) characters in the output, they need to be stripped from the result before the check. Or you can try array notation since they are returned in a dynamic array: ExCmpFiles.$CommandOutput<1>=1 One of many deeper discussions here for your dining and dancing pleasure. :...

sinhasaurabh014 wrote:I have done migrations from 8.5 to 8.7 to 9.1 to 11.5 and practically have not faced any issue so far.

Sounds like you followed a Best Practice path more closely. That would definitely help minimize the issues the OP is finding.

Didn't mean you literally had to test every single job (a bit of hyperbole on my part), just that a significant testing effort should be part of your migration. I would try to put together a list of job types, jobs with the same combination of stages, for example. Or jobs that use a certain stage in...

It only needs to be multi-instance is they all need to run at the same time. Your need sounds like a Sequence job looping a normal job to me.

Because it's still a RAC cluster. It doesn't know nor care how many nodes there are.

MCM - because only one client can be active at any given time.

Let me make a few points, not from having experienced any of this myself but rather from reading every dang post made here since 2002 and seeing this over and over when people upgrade from the 8.x world. By "this" I mean the issue of things that "worked" in 8 that no longer do. T...

I assume you are talking about the step to import the table metadata from Oracle, yes? Regardless, it's been a very long time but it sounds to me that you may be connecting to a specific instance in the RAC cluster rather than the "RAC name" - the service name of the cluster itself.

Typically, a records "splits" like that when a large text field has record limiters in it. And typically that's because it has either been hand-typed by a user who it trying to make it "all pretty" or it has been pasted from a document into the database. Any chance of that, a str...

Well... not exactly my forte but according to the wiki page that code page does not have "complete support" for French. You might want to try switching to one of the others listed that do. If that doesn't help, I'd be curious what your custom routine is actually using to send the email... ...

Ah... nothing like old mainframe developer humor. :D

... or that.

I'm curious why the mention of "hexadecimal" and showing the source field value as x'058c' when a COBOL COMP field is binary storage. That seems like a disconnect to me... but then it's been a long time since I've actually had to deal with an EBCDIC file.

How exactly is the file being unzipped "at the job level"? If you are sending it to standard out then you should be able to pipe it to something like "sed" to remove the first record before the job consumes it.

Ah... it's the simple things we forget first.