Any help or tips on writing a .cpy file?
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
cobol copybook
Collapse
X
-
cobol copybook
I'm sorry, but I'll make no apologies for this
Pogle is awarded +5 Xeno Geek Points.
CUK University Challenge Champions 2010
CUK University Challenge Champions 2012
-
-
What kind of tips? It's just COBOL.Originally posted by Pogle View PostAny help or tips on writing a .cpy file?
I suppose it's even more important to use a unique prefixing system for all field names, to avoid duplication, but you should be doing that anyway.Comment
-
Copy replacing - if supported by the compiler in question.Originally posted by expat View PostWhat kind of tips? It's just COBOL.
I suppose it's even more important to use a unique prefixing system for all field names, to avoid duplication, but you should be doing that anyway.Comment
-
* copybook INQINTC
* Channel name
01 INQUIRY-CHANNEL PIC X(16) VALUE 'inqcustrec'.
* Container names
01 CUSTOMER-NO PIC X(16) VALUE 'custno'.
01 BRANCH-NO PIC X(16) VALUE 'branchno'.
01 CUSTOMER-RECORD PIC X(16) VALUE 'custrec'.
* Define the data fields used by the program
01 CUSTNO PIC X(8).
01 BRANCHNO PIC X(5).
01 CREC.
02 CUSTNAME PIC X(80).
02 CUSTADDR1 PIC X(80).
02 CUSTADDR2 PIC X(80).
02 CUSTADDR3 PIC X(80).VS/COBOL IIIDENTIFICATION DIVISION.
PROGRAM-ID. CLIENT1.
WORKING-STORAGE SECTION.
COPY INQINTC
PROCEDURE DIVISION.
MAIN-PROCESSING SECTION.“Brexit is having a wee in the middle of the room at a house party because nobody is talking to you, and then complaining about the smell.”Comment
-
Flippin' heck! That brings back memories!
But aren't we talking COBOL V+ these days? Even I was working in COBOL III before I finished..."I can put any old tat in my sig, put quotes around it and attribute to someone of whom I've heard, to make it sound true."
- Voltaire/Benjamin Franklin/Anne Frank...Comment
-
BTW Does anyone know what happened to JJ Le Burt? I had his bible for Cobol II and Cobol 3 but he didn't write anymore - I waited for later versions but they didn't appear...
"I can put any old tat in my sig, put quotes around it and attribute to someone of whom I've heard, to make it sound true."
- Voltaire/Benjamin Franklin/Anne Frank...Comment
-
-
Those level 01s really should have been level 77s. And should that customer number really have been alphanumeric and not numeric?Originally posted by darmstadt View Post* copybook INQINTC
* Channel name
01 INQUIRY-CHANNEL PIC X(16) VALUE 'inqcustrec'.
* Container names
01 CUSTOMER-NO PIC X(16) VALUE 'custno'.
01 BRANCH-NO PIC X(16) VALUE 'branchno'.
01 CUSTOMER-RECORD PIC X(16) VALUE 'custrec'.
* Define the data fields used by the program
01 CUSTNO PIC X(8).
01 BRANCHNO PIC X(5).
(I've got grey sideburns. Can you tell?)My all-time favourite Dilbert cartoon, this is: BTW, a Dumpster is a brand of skip, I think.Comment
-
From a language point of view the 01 v 77 is a valid arguable style point. However in a number of compilers there is good reason for using 01 rather than 77 related to the code that is produced.Originally posted by RichardCranium View PostThose level 01s really should have been level 77s. And should that customer number really have been alphanumeric and not numeric?
(I've got grey sideburns. Can you tell?)
Equally the first 4 items (assuming they are indeed constant) could have been defined as a level 78 (if supported by the compiler) or they could have been defined in the constant section (if supported by the compiler in question).
CREC should probably also be a typedef (if supported)
The code of the main program fails the full ANSI '85 syntax check as well for at least 1 reason (no data division - and it never was optional if any of the sections were used). If memory serves the standard did make the environment division optional.
Far too many bloody variations. Post 85 standard everybody has gone their own way a bit.
Anyway I could update it all to object cobol in no more than 250 lines of new code. There's progress.....Comment
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers

Comment