If using the IBM COBOL Set for AIX (or similar compiler), check for
MAP
and
LIST
compiler options. You may also want to compare the output with OPT and NOOPT. If you start at:
http://publib.boulder.ibm.com/infocenter/comphelp/v7v91/index.jsp?topic=/com.ibm.aix.cbl.doc/pgaix.htm...
Yes, you may include the info in your copy book.
So far, there have been NO "conforming" implementations created by any vendor.
I don't know of any "programmer oriented" books. (Actually, there is one, but it is in Dutch <G>).
Some day, I'll update the FAQ with all the information about it...
...file status codes for "traditional" ('85 Standard) COBOL, I have now added a FAQ with (all the excruciating) details of "standard" file status codes from the '02 Standard.
This includes new
- 0x *> implementor defined succesful
- file-sharing / record-locking
and some others.
Bill...
...and
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/igy3pg31/2.4.53.2
***
However, be aware that these results are NOT the same in all implementations that allow storing X"FFFF" in a two-byte binary field.
Bill Klein
...there are some new ones in the '02 Standard (and some new implementor defined ranges). The following information is from the '02 Standard:
********
I-O status expresses one of the following conditions upon completion of the input-output operation:
1) Successful completion...
It may be in the thread somewhere, but if you are using a compiler that reats COMP the same as USAGE BINARY (which many do - but not all) *AND* you are running in "standard conforming mode" then it is true that a field like:
05 Num1 Pic S9(5)V99 COMP.
will "truncate" above +99999.99 or...
If you are using a current IBM mainframe compiler, then make certain that you understand the differences between
DBCS
and
Unicode
Checkout the
- NSYMBOL compiler option
- The NATIONAL-OF and DISPLAY-OF intrinsic functions
- What "CCSID" means on an IBM mainframe system
All of these...
Also, all the Micro Focus documentation is availabe (for free) online.
Check out:
http://supportline.microfocus.com//documentation/index.asp
Bill Klein
What compiler?
What operating system?
(Depending upon the answer to these questions, this may be semi-easy or semi-hard or virtually impossible)
Bill Klein
...does not impact the particular quesiton of "passing" index settings to other programs, it can definitely impact some inter-program semantics.
***
P.S. For Tom,
In the '02 Standard (not the '85 Standard)
LOCAL-STORAGE
items get "pushed and popped" upon EXIT PROGRAM (EXIT METHOD and...
Althugh I am aware that some vendors do have extensions allowing OCCURS at the 01 (and some at the 77) level, there are some reasons - not just historical for NOT allowing this. The most obvious (to me) reason has to do with questions of what happens if you allow it for 01-levels under and FD...
To the best of my knowledge, EVERY Micro Focus product since about 1995 has required run-time licenses for ALL applications.
I suggest that you check the license agreement, if you have any question about what is and is not legal to distribute without paying run-time licensing fees.
Bill Klein
Have you talked to MF about it? Again, it is my understanding that they do hvae some "bundles" (and individual developer prices) that MIGHT meet your needs.
Bill Klein
For a 60 to 70 "end-user" situation, you MIGHT also want to contact your Micro Focus "sales representative". I believe that they have "multi-licensing" deals that MIGHT make this more cost-effective than a conversion from one vendor's COBOL to another (depending upon how many Micro Focus...
...international programmer, you can ask what PIC N means.
FINALLY, you can ask about non-Standard items like COMP-whatever, Usage POINTER, etc.
***
almost all COBOL pc compilers that I know of, have some documentation on how THEY handle these issues. Read YOUR documentation and then...
...When Other
Display "Invalid Second byte:" IH-Byte-2
Set Error-Occured to true
End-Evaluate
*
Evaluate True
When IH-Byte-1 Numeric
Compute Sixteens-Place = Function NumVal (IH-Byte-1) * 16...
OOPS,
Please realize that my last reply was WRONG, given the input description that you give us. You said that the input would be in "hex" (2 characters), e.g
00 = X'00'
BUT
AB = (some charcter)
would also be valid. Therefore, to use the approach I suggested, you need to
A) allow...
The IBM COBOL for OS/390 and VM (and later IBM MVS and OS/390) compiler all support the ANSI/ISO 1989 Intrinsic Functions module. They do not, however, support one byte binary fields (which I don't think is really necessary for this).
Consider using the folloiwng (compatible across platforms...
This also MAY depend upon which release/version of
- COBOL
- PL/I
- Language Environement
you are using. There are DEFINITE differences in what is and is not allowable for COBOL / PL/I ILC depending upon what release and version of each of these you are using.
Bill Klein
Given the code snippet
03 TABEL1 VALUES ZEROES.
05 XITAB1 PIC S9 OCCURS 10 TIMES INDEXED BY XI1.
03 TABEL2 VALUES ZEROES.
05 XITAB2 PIC S9 OCCURS 10 TIMES.
My guess is that you (or the original coder) is not (was not aware that with any ANSI '85 Standard conforming...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.