Search results for query: *

What! Doesn't anyone else have to look at old nasty code on occasion like I do!! What about generated code kicked out by some "half baked" translator to convert Assembler to COBOL.......I'm the only one! MAN! Actually that may be a bit overstated, more often than not I see well...

I would tend to disagree with you there nontrad....be very careful when not using the perform thru statements. I have been on the other side of the coin with problems related to open ended performs and goto's alike. s-)

That's it!! s-)

If you do not need to worry about century "19", then you could simply move your accepted date into another date field with "20" hard coded as the century. 01 SYSTEM-DATE. 03 TODAYS-DATE. 05 YEAR PIC 99. 05 MONTH PIC 99. 05 DAY...

What about displaying the contents of the field to actually see why it is abending......the if numeric check should work. s-)

Thanks Jack! At long last I was able to get some sort of output......although, the manner in which you got to it still has me chasing my tail a little. I displayed the program name inside of your perform varying loop and was able to come up with a chain of load modules. Where it goes from...

Darn, shoot, gosh, heck! Ok, still getting compile errors. Entry does not seem to be a cobol defined word in this context. It also does not like the program name reference. My cobol statements are as follows, and again I named the program cobol5: 0000-MAINLINE...

Ah......Thanks, I will try that. No I was not, this has just been a sort of "when I feel like it" project. If if fact it does work, it is very slick! Thanks again! Thanks, s-)

Jack, As far as providing the code goes, I am using exactly what you gave above. I set up a five level call chain of programs that do nothing more than display their name and call the next one....until I get to the 5th module. That is where I plugged your exact code in and am trying to get...

Jack, I am trying to get the code you suggested above to work, and am running into a few problems along the way. Could you please provide a little more information, specifically with regards to the first line of code: set procedure-pointer ws-ptr-my-ep entry 'mypgmnm' Procedure-pointer, as...

Is this a one time deal, or is it a necessity for every calling module during your batch run? Adding a parm to pass the callers name could be one way to go about this, or, to find out who is calling the module in a specific situation, force the module to abend and look at the calling chain in...

An easy way to get the displays that slade was talking about after each of your paragraph headings is with the COBTRACE command. By typing COBTRACE ON on your command line, displays will automatically be inserted at each paragraph heading and exit. Once you are finished with them, simply type...

If all you are looking for is an example copybook.......here ya go! 01 PKLR1-DETAIL-LOAN-RECORD. 10 PKLR1-BASIC-SECTION. 20 PKLR1-SORT-CONTROL-FIELD. 30...

It sounds like you may be able to use reference modification. This code was used to parse a generic file that contained information separated by a comma. Reference modification is formatted as follows: FIELD (LOCATION : LENGTH) INITIALIZE COUNTERS. MOVE...

Multiple record types definately sounds like the answer to this. I am not sure if it is the case on all versions of cobol, but from what I have seen, occurs depending is invalid and not allowed within another occurs depending on. s-)

Then the previous post was only half correct....a picture clause of S9(7) will take 4 bytes, however, a picture clause of S9(9) will take 5 bytes....

It is also possible to have the new files created even if the second step abends, however, the files would obviously not contain all of the relevant data. A backup step is definately the answer. But if you want to keep the new files whether the job abends or not, try coding the disposition as...

It should be as simple as changing your 'CH' in the include statement to 'BI' (Binary). Other legitimate values for this include condition would also be PD, Packed Decimal, ZD, Zoned Decimal and, I believe, FI, Fixed Integer. Hope this helps. s-)

Actually HRayT, a picture clause of S9(7) will occupy 7 bytes, as well as PIC S9(9) taking up 9 bytes. This is the case unless the numeric fields are defined as comp or comp-3, etc.