DSXchange

Simon, it looks like you seek functionality that doesn't exist: debugging access to the data being processed while the job is running. DS provides Peek and other debug stages, but I don't see that helping you. The only workaround I can think of is to insert copy stages at the points where you want t...

Don't be afraid to experiment. I had similar beginner's questions at one point, and Ernie's seemingly vague (high-level!) responses were actually very helpful. I'm working in 7x, so I don't know if this is still true, but I was able to import the schema using sample xml data files in the expected fo...

Gods, sometimes I hate Google. It thinks it knows better than I do what I want. :?

Anyway, found this: http://www.tek-tips.com/viewthread.cfm? ... 04&page=66

In other words, PIC 1(8) would be the same as PIC 9(1) COMP-5.

Let me know if that works.

I'm unfamiliar with the clause PIC 1 (#). Is there a usage clause in the Cobol code for the field in question? Anyway, I'm not sure how helpful I can be without understanding the storage format you are facing under EBCDIC. One thing I do know in 7x, there is darn little help converting raw binary to...

It depends on where the '\n' is causing you the trouble. Without seeing your code, I would expect one of two possibilities: 1) If you don't control this until the file stage, that is where you set the alternate value for end-of-record, in Format/Record level/Record delimiter string. After that, you ...

An old trick I learned from an assembler programmer that seems good regardless of the envirnoment: 1) Use some other special character for the end-of-record mark, one you are sure will not appear in the rest of the data. 2) Go ahead and remove all '\n' from every record. 3) Convert the end-of-record...

Thanks, Craig. That means any advice I may offer here could be inaccurate. MarbinPR, please take note.

I don't have a sample that comes close to your situation, but I do have a question for our gurus: If the OS is Windows, does that mean that the DS runtime environment is running on a Windows server, or is it still on a Unix server? That said, the times I've run into this sort of problem I've looked ...

As can often be the case, it was (developer) user error that created the problem.

It turns out that there were more than two new columns added to the DB2 table, and the SP parameters had to have places for them in the call and return set. Adding those columns to the output schema did the trick.

I and the person for whom I'm asking this are new to SP stages in general, this being an "inherited" job that needs enhancement. We are open to the possibility that this is a problem on the DB2 side, though it doesn't look that way so far. Existing SP was in use with no problems. Two colum...

Based on what you wrote in your post, you might be misunderstanding how the decimal attribute is applied to the data. For example, your first field (if I read you correctly) should be ( 4 ,2), not (2,2). Your field length is four with two positions to the right of the decimal. If I'm correct, that's...

http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/index.jsp?topic=/com.ibm.swg.im.iis.ds.zosfilestage.doc/topics/overview_zosfile.html According to that page, if you can read from z/OS to Unix with the Zos file stage, you should be able to write to it. You might have a problem with something o...

I'm surprised that a multi-platform environment considers FTP "not feasible". From what I've seen (not a lot, I should admit) FTP is the cheapest and most stable option for moving files to and from z/OS and Unix. Sometimes "We can't do that" becomes a grudging "Okay, we'll d...

That's just cool, Donny. I haven't learned something new in COBOL in ages. I found an old Merant (MicroFocus) reference for comp-6 at http://esd.netmanage.com/Documentation/books/sx20books/cgrmdf.htm . My MicroFocus reference is old and doesn't mention comp-6. I suggest experimenting. Try what I des...

That's certainly true in 7.5.2.

I'm an old COBOL dog, so I don't hesitate to edit the copybook before importing it, deciding on arrays and redefines myself. When I deal with mainframe data, it's always going to or from some other platform (usually Unix) where COBOL formatting is not very useful.