Mainframe cobol interview questions. How can we eliminate junk value in field I am guessing, but it looks like you may be reading variable length records from a file into a fixed length. COBOL record. The junk. Sorting In Cobol Program' title='Sorting In Cobol Program' />COBOL record is giving you some grief. Hard to say how consistent that junk is going. That junk ends up. Sorting In Cobol Program' title='Sorting In Cobol Program' />WSAMOUNTTXT after the UNSTRINGThere are a number of ways to solve this problem. The suggestion I am giving you here may not. The last INTO field, WSAMOUNTTXT, in your UNSTRING statement is the one that receives all of the trailing. That junk needs to be stripped off. Knowing that the only valid characters in the last field are. PERFORM VARYING WSI FROM LENGTH OF WSAMOUNTTXT BY 1. UNTIL WSI ZERO. IF WSAMOUNTTXTWSI 1 IS NUMERIC OR. WSAMOUNTTXTWSI 1. MOVE ZERO TO WSI. MOVE SPACE TO WSAMOUNTTXTWSI 1. HUb2ygrQR50/S7yDj9s470I/AAAAAAAAD1Y/Bw-itmCksto/s640/VisualCOBOLCompare.png' alt='Sorting In Cobol Program' title='Sorting In Cobol Program' />The basic idea in the above code is to scan from the end of the last UNSTRING output field. Once a valid digitdecimal is found, exit the loop on the assumption that the rest will. After cleanup use the intrinsic function NUMVAL as outlined in my answer to your. WSAMOUNTTXT into a numeric data type. One final piece of advice, MOVE SPACES TO INPUTREC before each READ to blow away data left over. This will protect you when reading a very short. Hope this helps. EDIT Just noticed this answer to your question about reading variable length files. Using a variable length input record is a better approach. Given the. actual input record length you can do something like UNSTRING INPUTREC1 RECLEN INTO. QvdFWqMlMg/Sp3fN3rKFtI/AAAAAAAABN0/FZ3dn5UDBPo/s800/COBOL%201.23.png' alt='Sorting In Cobol Program' title='Sorting In Cobol Program' />Where RECLEN is the variable specified after OCCURS DEPENDING ON for the INPUTREC file FD. All the junk you are encountering occurs after the end of the record as defined by RECLEN. Using reference modification as illustrated above trims it off before UNSTRING does its work to separate out the individual data fields. EDIT 2 Cannot use reference modification with UNSTRING. Darn. It is possible with some other COBOL dialects but not with Open. VMS COBOL. Try the following MOVE INPUTREC1 RECLEN TO WSBUFFER. UNSTRING WSBUFFER INTO. Where WSBUFFER is a working storage PIC X variable long enough to hold the longest input record. When you MOVE a short alpha numeric field to a longer one, the destination field is left justified with spaces used to pad remaining space ie. WSBUFFER. Since leading and trailing spaces are acceptable to the NUMVAL fucnction you have exactly what you need. I have a reason for pushing you in this direction. Any junk that ends up at the trailing end of a record buffer when reading a short record is undefined. There is a possibility that some of that junk just might end up being a digit or a decimal point. Should this occur, the cleanup routine I originally suggested would fail. EDIT 3 There are no in the resulting WSAMOUNTTXT, but still there are a MLooks like the file system is treating lt CR that M thing at the end of each record as data. If the file you are reading came from a Windows platform and you are now. DateDiff in cobol using SELECT satement. Assembly. For maximum compatibility, this program uses only the basic instruction set. Bubble Sort 01112014 23062016. Java Data Structures 2nd Edition End of the World Production, LLC. SYNCSORT program examples Examples of some of the things that you can do with Syncsort PGMSORT SORT01 EXEC PGMSYNCSORT SYSOUT DD. UNIX platform that would explain the problem. Under Windows records. CR lt LF while on UNIX they are terminated with lt LF only. The. UNIX file system treats lt CR as if it were part of the record. If this is the case, you can be pretty sure that there will be a single lt CR at the. There are a number of ways to deal with this Method 1 As you already noted, pre edit the file using Notepad or some other. CR characters before processing through your COBOL program. Personally I dont think this is the best way of going about it. I prefer to use a COBOL. Method 2 Trim the last character from each input record before processing it. The last. character should always be lt CR. Try the following if you. Swf To Screensaver Scout Keygen. SUBTRACT 1 FROM RECLEN. MOVE INPUTREC1 RECLEN TO WSBUFFER. Terra Revolution Zip. UNSTRING WSBUFFER INTO. Method 3 Treat lt CR as a delimiter when UNSTRINGing as follows UNSTRING INPUTREC DELIMITED BY, OR x0. D. INTO WSID1, WSID2, WSCODE, WSDESCRIPTION, WSFLAG, WSAMOUNTTXT. Method 4 Condition the last receiving field from UNSTRING by replacing trailing. I outlined this solution a litte earlier in this. You could also explore the INSPECT statement using the REPLACING option Format 2. This should be able to do pretty much the same thing just replace all x0. SPACE and x0. D by SPACE. Where there is a will, there is a way. Any of the above solutions should work for you. Choose the one you are most comfortable with. COBOL DB2 Program Introduction. Mainframes 3. 60. First, you need to declare the Cursor Query. DECLARE C1 CURSOR FOR is the statement used to declare a cursor. I am going to declare a cursor, which can retrieve Employee id, name, salary and joining date from the Employee table. You also need to supply the SQLCACOBOL Variable, that shall hold the results of the OPEN, FETCH and CLOSE Cursor operations. You want to be sure, that OPEN, FETCH and CLOSE Cursor operations go clean, without any errors, so you need SQLCA to check on that. You generally type an INCLUDE SQLCA entry. Now, you begin type executable COBOL Instructions in the PROCEDURE DIVISION. Essentially, the task of fetching data rows from the DB2 Table can be divided into 3 paragraphs 1. OPENing the Cursor 2. FETCHing data from the Cursor row by row and 3. CLOSEing Cursor. I have typed the MAIN Paragraph in the PROCEDURE DIVISION like this   Line 3. Open paragraph, to open the cursor. When you do a FETCH in SQL, it returnsretrieves back the row, the cursor is currently pointing to. Every time you FETCH, the current row is returned, and the cursor is incrementedset to the next row. A SQLCODE0 signals a successful FETCH. This sequential row after row process of FETCHing, continues on and on. But, how do you know, how many rows you want to fetch 5, 1. You dont The situation where the cursor points to the Last row, and there is no more data to get, is detected using the special SQLCODE1. A SQLCODE1. 00 is the special, exceptional condition, where the cursor points to the last row, and there are no more data rows to FETCH. You should do as many FETCHs until, you hit SQLCODE1. Line 3. 8 in the PROCEDURE DIVISION, performs FETCH paragraph to get one row at a time, repeatedly until SQLCODE is set to 1. Line 3. 9 performs the Close, to close the cursor. To Open a Cursorand execute the Cursor query, in SQL you type OPEN cursor name. I have coded 1. 00 OPEN Paragraph below, which executes the SQL instruction, OPEN EMPCSR on Line 4. When you OPEN EMPCSR, it means SELECT EMPID,ENAME,SALARY,JDATE FROM EMPLOYEE query will run. The results will be stored in a SQL Area EMPCSR. The contents pf the Cursor Area EMPCSR are 1    RAM    1. RAJ    2. 00. 0    2. RAKESH 3. 00. 0    2. A marker or a pointer is set to the first row in the Cursor Area. This pointer position, tells whats the next row to be read To fetchreceive data rows from the SQL Cursor area into the COBOL Program, in SQL you type FETCH cursor area name INTO  COBOL variables The 2. FETCH Paragraph from Lines 4. Cursor Area EMPCSR. So, this reads the row 1   RAM    1. But, when this data arrives in the COBOL Program, where is it stored So you also supply a list of COBOL Variables corresponding to each SQL Data value received. In the picture below, EMPLOYEE ID COBOL Variable will receive the value 1, EMPLOYEE NAME COBOL Variable will receive the value RAM,  EMPLOYEE SALARY COBOL Variable will receive the value 1. EMPLOYEE JDATE COBOL Variable will receive the value 2. FETCH cursor area name is a SQL Instruction. When you want to use COBOL Variablesnon SQL Variables like EMPLOYEE ID, EMPLOYEE NAME etc. SQL Instruction, you prefix them with a Colon. I have DISPLAYed the recently fetched EMPLOYEE INPUT RECORD. After the FETCH Operation is completed successfully, the SQLCODE is set to 0. The pointer is incremented and set to the next row in the cursor area. RAM    1. 00. 0    2. RAJ    2. 00. 0    2. RAKESH 3. 00. 0    2. The 2. 00 FETCH Paragraph is performed over and over again, till youve read the last row, until SQLCODE1. The 2nd FETCH will store 2 in EMPLOYEE ID, RAJ in EMPLOYEE NAME, 2. EMPLOYEE SALARY and 2.