DSXchange

I'm an East Coast COBOL dinosaur, ff. Started in 1990, and about 80% of my ETL development is for MF data dependencies.

I keep forgetting that the using MF data FAQ is linked in my post signature. I wrote it (pats self on back) and you may find it helpful in a general way.

Updates on things learned: Paul, the datasets are all newly created in the current cycle. Migration is not an issue, but I do have observations that it would not cause this sort of performance loss. qt_ky: Interesting suggestion, but it can't fit, because MF-Unix connectivity is very different from ...

Paul, Single server/gateway, with load balancing dynamic on three LPARs. EDIT: server configuration limits number of data ports in use, and has disabled the active/passive command attribute. I've confirmed that this is not a data port issue. There's no gateway (or firewall) between the Unix server a...

Remove the "V" from the PIC clause, where it appears after the close parentheses. Before you import, though, decide if you actually need the redefinition of the field. If you need one "version" but not the other, make it the primary line and remove the REDEFINES clause. If you ne...

Hoping that someone may have had anything similar, about which you can share any details with me here. The situation: We have jobs that loop through FTP sessions, one at a time, to get mainframe datasets and land them on our DataStage server. Tracing indicates that ACK is delayed, with only 3 or 4 d...

Some preliminary questions: What is the actual copybook definition for the record? I ask because "DISPLAY_NUMERIC" is a subset of alphanumeric, just restricting the valid values to numeric characters. It will have explicit bytes for the sign, commas and decimal, and sometimes DataStage wil...

My French is sufficient to understand your request, but not to reply to you in French.

The simplest approach is to select the date into a user variable stage at the beginning of the job sequence. That variable then becomes available to every stage after.

Some basic questions you may already have covered. My intention is to isolate the potential causes. Have you done a simple replacement of the connector channel? By this I mean writing to a local file, using FTP to land the data on the mainframe, or setting up a test channel with some other DBMS like...

It depends on the priority of the conditions. If a condition you know to be true is not being evaluated, it's because a lower priority condition is true first. Break out your logic into single statements, and do a final logic check based on the priority of the true conditions. Or, as I've found help...

What's the rental fee? :) I assign no fault to anyone faced with mainframe and especially Cobol formatted data for the first time or without any background in mainframe development. I've been dealing with EBCDIC to ASCII for 27 years, and it still finds ways to trip me... or is that trap me? One of ...

Gently, Craig. Ask me to tell the story of the four-page nested IF statement that compiled perfectly and never worked. :wink: DataStage is just not friendly. It gives me many of the same conniptions as Excel, and the leading zero thing is on the short list. ffsw, I suggest going back to the data for...

Franklin trots out his Cobol soapbox... :wink: Question the data. Look at the format and ask: was this particular design choice actually necessary? A single digit designating century is far from standard. The first lesson learned out of the Y2K fiasco is that the days of restricted or expensive stor...

Franklin, the table definition of sequential file has first row as header, checkbox. I had read these as columns into FTP enterprise. Yes, header reads first row as data row. That should be it, then. You're expecting a sequential file stage read, and FTP doesn't conform to the same processes. Looks...

My questions need answers if I'm to help further. I checked FTP Enterprise and didn't see anywhere to set for first row headers. It looks like the stage is reading the header row as a data row.

What's the actual format of the file you are transferring? What does the header record look like?

Often, the OSH/DataStage column attributes are just off in some way. You are reading external data, and the import is seeing something unexpected. You need to identify that attribute.