Search results for query: *

Any paradigm can produce a mess if poor coding techniques and convoluted logic are used. Jay

VSAM status codes can be obtained from your COBOL or COBOL/II Language Reference. Jay

There is an easy way. The following assumes you are using QMF (embedding in a high-level language will require setting up a CURSOR): SELECT NAME FROM SYSIBM.SYSCOLUMNS WHERE TBNAME = 'name of table or view' Jay

Assuming you have it in electronic form, I'd search for the string "GAGETRAK" or just "GAGE" or "TRAK". Also, are you certain that all of the programs/sub-programs are COBOL? That single character "C" at end makes me suspiciouis. Jay

If there isn't any functional documentation, the message text would be in the source code. It might be built from variable elements, complicating its detection. If you don't have the source or any documentation, you might be able to determine this by searching the executable code, although...

What environment are you operating in? Also, have you eliminated the possibility that the message is application-specific (generated by program logic, as opposed to the compiler or operating system)? Jay

I haven't done this in while, so I'm relying on memory. Each SAL operation would shift the entire contents left by 1 bit, essentially doubling the current value until the first ON bit falls off the left side. For example: 0000 0000 0001 0000 (dec 16) 1st SAL leaves 0000 0000 0010 0000 (dec...

There are some machine instructions which may be essential to the proper operation of a driver that a high-level language may not be capable of generating. Jay

Excellent example of the object-oriented paradigm. Regards, Jay Jay

Write a separate query with the same selection criteria as your cursor, but only SELECT COUNT(*). Jay

Not surprising; Hursley is IBM's CICS development lab. Jay

You do need to move the fields around. 3270 tabbing is strictly horizontal, with line-wrapping. Jay

I got so caught up in the other issues that forgot to clarify my original point, which is that I don't think "GO TO"s really add much clarity and avoiding them is more a case of getting practice in developing good logic habits than anything else.

Jack, I think you may have misunderstood some of my post. I probably didn't make my point clearly enough, as I agree completely with your 4-19 post regarding the importance of proper logical structure. Other than technically irrelevant stylistic differences in the formatting of data...

Two comments regarding "GO TO" vs. "PERFORM": 1. Rather than having the first statement in a paragraph be "IF condition GO TO EXIT" you'll achieve greater efficiency and readability by coding "IF condition PERFORM". IF PROCESS-ME...