Search results for query: *

Hi, You can try this; Define your record field as: PIC 9(6).99. (use your orig value - 028238.24) Code the receiving field as: PIC ZZZ,ZZ9.99. Then, MOVE rec-fld TO recv-fld I haven't tested, but the manual says num-ed to num-ed is permissable. Regards, Jack. "A problem well stated...

Hi David, I've been viewing this thread on & off since the beginning. Unfortunately I have no answers for you, but I have a few ques if you haven't yet left the building; 1) I noticed your "before" run shows the 3rd line truncated. Typo? 2) Are you viewing the problem SYSOUT using the SDSF...

Oops, I forgot the POINTER in the 1st unstring. Regards, Jack. "A problem well stated is a problem half solved" -- Charles F. Kettering

Hi, If your compiler supports reference modification, you might try 2 unstrings or one followed by a ref moded move. In either case the 1st unstring uses POINTER. Use the pointer to ref mod the 2nd unstring or the move, e.g.: 1st unstring addr-fld delimited by ' ' into st-nbr 2nd...

Does JS01.CNTL.LIB2(BJSJSA10) contain a valid JOB card? If it does you shoulb be able to find that JOB's exec info (JES/SYSMSG, JCL, etc.) on the sysout Q. Regards, Jack. "A problem well stated is a problem half solved" -- Charles F. Kettering

Hi CCFC, You haven't provided enough info about the exec of the JCL and the Abend. If you can, copy and paste the listing produced at executiona and the info surrounding the abend. At this point ew don't need the dump, just the msgs and any msg #s, for ex., "IEFxxxnnn: ERROR OPENING FILE...

Why, thank you Razalas, it's appreciated. Regards, Jack. "A problem well stated is a problem half solved" -- Charles F. Kettering

One other thing to keep in mind: If any of the 01s is a different length than the others, the compiler assumes that the file is variable length. Therefor, you must WRITE the appropriate rec to assure that the correct length rec is written. If they all are the same length you can WRITE any of...

Hi Jim, If the like-valued JOB-NAME fields in the table are in succession as shown in your post, here's a sleight variation on Glenn's idea that may help (untested): When you get a search hit, set an increment(INCR) field to zero and PERFORM the hit code you have in mind adding 1 to the INCR...

If your Compiler supports the INSPECT verb and the REVERSE Intrinsic Function you can try something like this (untested): 01 L PIC 9(02). 01 WRK-ZIP-FLD. 05 WRK-ZIP-1 PIC 9(05) 05 WRK-DASH PIC X(01) 05 WRK-ZIP-2 PIC 9(05) INSPECT...

Hi Markus, It sounds like you have a VSAM file that contains records that have comp-3 fields w/PICs that vary from S9V9 to S9(09)V9(09). Why don't you show us some recs in the file and the file record description. It might give us a better insight into the problem you're facing...

How are the fields defined? Regards, Jack. "A problem well stated is a problem half solved" -- Charles F. Kettering

If you are working on an IBM M/F system modify and re-compile your pgm by including a non-zero VALUE for the COMP-2 field and making the first 2 PD stmts:DISPLY '>' yr-comp2-var-name '<' STOP RUN Use SDSF to look at your execution SYSOUT; turn HEX ON; and it will give you an idea of how the...

Hi Mani, What is a z900 hex format? Can you provide a link where it's discussed? Thanx and Regards, Jack. "A problem well stated is a problem half solved" -- Charles F. Kettering

No mikrom, you learned something OLD. :-D Regards, Jack. "A problem well stated is a problem half solved" -- Charles F. Kettering

John, Could you define 2 fields; 1 for the DISPLAY, 1 for the arith. E.g.: ARITH-FLD pic 9(008). DISP-FLD pic z(007)9. ACCEPT ARITH-FLD MOVE ARITH-FLD TO DISP-FLD Regards, Jack. "A problem well stated is a problem half solved" -- Charles F. Kettering

If your compiler supports reference modification you can DISPLAY TEST(1:1) displaying the 1st digit of the field or DISPLAY TEST(2:1) displaying the 2nd digit of the field. Regards, Jack. "A problem well stated is a problem half solved" -- Charles F. Kettering

Hi RK, Here's a few links I had laying around that may be helpful. http://publib.boulder.ibm.com/cgi-bin/bookmgr/SHELVES/ispbkm10 http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/ISPZEM40/CCONTENTS <http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/ISPSER04/> Regards, Jack...

Hi rusherke, You don't mention your environment, but I'll assume IBM zOS/eCOBOL. Since using a cursor is akin to creating a seq file from table data, I usually put the cursors in WS. I see you have them in the code - may be a problem, maybe not. You say "make a cursor in a cursor", I like to...

Hi Greetz, One other point for you to worry about (the following assumes a fairly recent IBM COBOL Compiler): As I recall, CSV files can have records of variable length. Yours may not because of the business aspects of the data. But others may want to keep this in mind. The way I remember...