DSXchange

They're different. Business Glossary is the database of business terms and their definitions, related terms, usage, examples, abbreviations, stewards, history and so on. It can be searched using the Business Glossary Browser. Business Glossary Anywhere is a widget that can reside on any desktop. Onc...

Create a routine that uses ReadBlk statements.

IsValid() function needs to be applied to the string before any conversion is attempted.

The result of the command includes a newline. Try eliminating it, for example by changing the command to

Check that the SAP PACK was correctly installed. THe routine named belongs to that PACK.

The problem is between the keyboard and the chair.

Somewhere in server 2 the job name SEQ_X does exist, whether it's simply in an index that needs to be updated, or hidden in some archive category.

Use Quick Find to find it. If that doesn't find it, re-index the project.

The thought also occurs that your mainframe data may be encoded as EBCDIC. Can you please confirm one way or the other?

Then it is incumbent upon you to determine what these unwanted characters actually are. Initially you said line breaks. Then you gave an example with "<" and ">". What's actually going on here?!! Once you have found them, you can use Convert() to eliminate them. However, if the h...

Do you have Balanced Optimization licensed? This functionality could push the join back into the database automatically, based on a cost-based algorithm.

Can you be more specific about which stage type you are referring to?

Then read the chapter on this stage in the manual, and report back to us what it does, and why you believe it should be able to perform a vertical pivot.

Create the table with the base name only. In the controlling sequence rename the file once the job is done. Use one of the SDK key management routines to generate the sequence. (Reset the key value to 0 each time the sequence runs.)

I'm presuming you have engine, services and repository tiers on one machine. This combination is far more demanding of resources than the version 7.5 server (engine only). You're running out of memory when you run the big job. Solution is to add more memory.

If you remove ETL_DATE, do all fields propagate?

Have you tried it? What happened? In particular, how did you specify the Join key column(s).

Then the question you have to answer - which I already asked - is how did they get into the DB2 table?