cobol

We can't turn off the NUMCHECK option for our new COBOL V6.2 compiler because we can't trust the content of our numeric variables. The problem is, that when we turn it on, it's not fully compatible with the COBOL 4 we had previously at our organization. Specifically - when an unsigned packed variable contains X'123C' , COBOL 4 would have accepted it and let us continue, but COBOL 6.2 with NUMCHECK(PAC,ABD) abends, and only willing to accept X'123F'. This is a real issue for us regarding assembler invoking COBOL, or reading from files and etc. Is there another option or maybe even a PTF that

I have to preform 3 tasks: an insert, a delete, and a write I'm not sure what the best way to do this is. My mainframe program design skills aren't too tight, so I was looking for advice. Could I avoid doing a COBOL program for this? The way I see it, I just need JCL that executes SQL statements. If I design my statements correctly, then they should be able to preform tasks 1 and 2 this way. But I'm thinking I may need to have a COBOL program to write to a file? I'll overview my thought process for the 3 tasks. Each task seems similar, but they query different results, so the SQL statements

Is there any way that we can find the exact line number that causes an abend ( like SO4C) from the Offset(like offset +00007D0A at address 1515CD0A ) given in the spool with the error message.? If your program is compiled with options OFFSET,NOLIST, you will have a list of verbs/line numbers in the output listing which contain the "offset" from the start of the program. The line number on the the listing which has the closest offset, but less than or equal to, the "offset" reported in the abend, is where you want to look. If you use NOOFFSET,LIST, you will get the "generated assembler" in your

I am executing a standalone Enterprise COBOL program with the below calculation. I am having a COMPUTE with multiple operations and another with the full calculation split up. But the results are different(the last 4 digits) in both cases. I have manually calculated these using a calculator and the result matches the one with the split up COMPUTE statements. I have tried the calculations by using the entire answer at intermediate results and use only 15 digits of the final answer and also using only 15 digits at all intermediate steps(without rounding). But none of these results match with the

Very basic question here. I have to write out a data glossary for a COBOL program. This data glossary includes the following details about every variable: Name Data type Range of values (if applicable) Line numbers Fuller name I have several variables that include level 88 switches. My question is this: Are these level 88 switches counted as variables, and should I include them in the data glossary? Or, judging by the data glossary structure I have to work with, should they be ignored in this context? And while I'm here, another simple question. Should fillers be included in data glossaries?

Need to concatenate 4 strings to a destination variable in cobol. Like, 01 WS-S1 X(10) VALUE "HI ". 01 WS-S2 X(10) VALUE "HOW ". 01 WS-S3 X(10) VALUE "ARE ". 01 WS-S4 X(10) VALUE "YOU?". to a resultant string "HI HOW ARE YOU?" Can anyone please help me out? Here is a working example of the STRING verb that does what you are looking for: IDENTIFICATION DIVISION. PROGRAM-ID. EXAMPLE. DATA DIVISION. WORKING-STORAGE SECTION. 01 WS-S1 PIC X(10) VALUE 'HI '. 01 WS-S2 PIC X(10) VALUE 'HOW '. 01 WS-S3 PIC X(10) VALUE 'ARE '. 01 WS-S4 PIC X(10) VALUE 'YOU?'. 01 WS-CONCAT PIC X(43) VALUE SPACES.

I've been searching for s9(5)v99 but got different information and not really clear. Could someone shows how or the formula to convert. thanks What you have shown us here is the PICTURE clause portion of a COBOL data declaration. COBOL data declarations are a bit odd and take some getting used to. Here is a link to an introductory tutorial on COBOL data declarations . This should get you started. The PICture clause you have given in your question is defining a numeric item with the following characteristics: S - Leading sign 9(5) - 5 decimal digits V - Implied decimal point 99 - 2 digits after