DSXchange

Told to me by my Cobol instructor: never apologize for ignorance. It gives those of us with a little bit of knowledge a chance to look like geniuses. :lol: DataStage has a scheduling utility. Look it up in the manuals. It's rather primitive compared to external schedulers, and might suit you if your...

"Server side includes." The general use is to source in script lines that are common to scripts in use. In my experience, they are common function definitions -- get server name, verify existence of directories, etc. -- and in our DataStage environment they contain required common variable...

PaulVL wrote:So how about a loop in your master sequencer?

How would he exit the loop? It's an assumption, but he indicates that the job is time based.

Sounds like a design problem (ahem, call me Dr. Obvious) but not at the DataStage level. You need a scheduler with cyclic capabilities to control your job runs. If you don't have an external scheduler, the following might help you find an inconvenient alternative in DS. We use Control-M. I would put...

Pete, maybe I'm confused, but I ask respectfully if with exasperation why the heck you'd want to put objects from more than one project in the same package? The assumption here is that you are using the isx format for your exports. The dsx format is very clear in the first headers, that the objects ...

The notion of a user "controlling" a production job scares me more than a little bit. I hope you have controls over that which would prevent a user from creating a mess. In our environment, I'd use Control-M to pass the location(s) to the DS job. For example, I'd create a variable called L...

Ramesh's sample data prompts me to ask: where are you converting to or from EBCDIC and ASCII?

Review all your read/write attributes. I'm guessing this is a character set issue, not the format of the data stream.

See my signature line for using mainframe data FAQ link.

Patrick, The import interface with DataStage works well for Cobol, but it has a couple of flaws. The first one is that it is designed to basic, strict standards being expected, and Cobol has flavors. The second is that it tries too hard to be WYSIWYG, and doesn't quite succeed. I'm glad you didn't r...

You don't have a multiple record type file. You have one record of 180 bytes.

Sorry, but you're barking up the wrong tree.

Follow the link in my post signature to the FAQ for using mainframe data. From your description, you have one record definition in two parts, not a header record followed by data records. The clue there is in the descriptions. RDK00 is 26 bytes long, and RDK01 begins in position 27. Revert the 01s t...

First impressions: Excellent presentations and support from Dennis and his team. Next time, schedule it for 90 minutes or two hours. I know attendees have time concerns, but this was important topical stuff, and well worth the time. Flow Designer looks very exciting. The integrated source control wa...

For secure and reliable restartability, full (bulk) load is the first choice. Doesn't matter what DBMS you are using, or the structure of the table. For example: Job 1 -- bulk unload for backup/restore if "new" data cannot be fully loaded. Job 2 -- merge unloaded data with "new" ...

I want to encourage everyone who attends the webinar to discuss the new release here. Mostly, it's so I have a chance to see myself write (hear myself speak).

I have a loop that uses a list file with parameters, an index (increasing integer, controls the number of loops) and a file name. Each instance of the loop calls a parallel job to FTP get the named file. First read of list gets maximum index (number of loops). During the loop, the instance of the lo...

You have a logical paradox in your requirements: certain characters are to be removed, except when they are not to be removed. The difference is positional, which is why it's a paradox. Why must you preserve the characters on the inside? Is this a hard requirement (like an audit trail), or is it arb...