DSXchange

What Craig said, and for us it was the active setting on the FTP host server. It limits the number of available data ports, and as volume and usage increased here, we started seeing a gradual increase in abends on no ports available. Often, it was masked by the host deciding that the file wasn't fou...

Rumu, Craig likes to tease. You don't need to apologize. He has me to answer mainframe data questions, and ever since I wrote an FAQ for him he's been even more teasing. Ahem. 8) Your latest problem needs further definition. What fields are involved with your "weird" characters, and what a...

There's a level of detail in your situation, which you would not provide here, which prevents me from offering any specific feedback. If you have successful reads and processing, then you have the right solution.

Rumu, Your need to split the REDEFINES to a subordinate item (higher level number) is very odd. I have many successfully imported copybooks that have the PIC clause on the REDEFINES item. The expected period error is not one I can help you with. Sometimes, if you used copy/paste for the line, retypi...

I explained the format requirement in the third post on this page: every line must start in position 8. You can indent higher level number lines for ease of reading, but it's not required. If your copy/paste of the REDEFINES line is accurate, you have a space following the last hypen, ACCOUNT- NUMBE...

Rumu, Yes, what Craig said. A bit more seriously: you are now dependent on another development environment. You need them to notify you of any changes to the code (copybooks) on which your DS jobs are dependent. You then have to manually make the corresponding changes in the jobs that use the copybo...

I had to look up the P in a PIC clause. It is an obscure usage meant to enhance or reduce the scale of the numeric format. The import wizard is not perfect -- see my FAQ for using mainframe data. "999PPP" means that the 3-byte field is scaled up. A value of 123 will actually be 123,000. Be...

The text of your post doesn't indicate if what I'm about to say is accurate. I'm assuming it is. The copybook format expected by the import wizard is simple. The first 7 bytes -- character positions -- must be spaces. Position 7 can contain an asterisk to make it a comment line. The "0" of...

First, you have my sympathy for a mainframe development process that doesn't comply with basic standard practice. For a multiple record file, there is no such thing as an "optional" header. The important part is that you can edit the copybook before importing it to reflect the reality of t...

My implementation is z/OS mainframe, and we handle what you describe as you describe it. FTP Enterprise stage for input: Format tab: Record type = implicit Delimiter = none Character set = EBCDIC Data format = binary Allow all zeros = yes Packed = yes -- Check = no One column, SQL type Binary, Exten...

Your input columns are all VarChar(7), your output column is Decimal(5,2). You have two fewer bytes on output, and unless you either trim the string to 5 bytes or increase the decimal to 7,2 you will continue to have the warning.

Based on a copybook I use that is similar to yours, it should work. You only need one 01 line. You only need one 05 Header section. You're import will show the redefines for the 05 body sections. The 05 trailer will show at the end. When you load the table definition to CFF, and you define it as mul...

That's a good start. You have 4 types of records, each with a unique value in RDT-REC-CODE. Every record type has a common area, 82 bytes "header" and the trailer. Your copybook can be reviewed to make sure on import that you've correctly loaded a table definition for each record type. Loa...

I'm not sure what you're asking, so let me know if I missed what you need. The copybook text file can have any extension. The import wizard for COBOL FD finds copybook files for import with the default extension .cfd, but you can have it find any other extension. The copybook is plain text and is co...

Rumu, There's a link to the FAQ for using mainframe files at the bottom of my post. To answer your last question first: the import wizard for COBOL FD looks for .cfd on file names. I've never tried using a formatted file like a Word doc, but the wizard is a plain text parse and you are well-advised ...