× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Howard.

This is indeed strange.  I have tried exactly your code on my AS/400, and it works with no problems!  Are you sure that you don't have other situations causing this message ( level checks on files, files not found etc).

Anyway, you can try to define your working-storage fields like this(just to see if it makes any difference):


......-A+++B++++++++++++++++++++++++++++++++++++++++++++++++++++++
       WORKING-STORAGE SECTION.
        01 WS-NEW-RECORD.
                 05 WS-TMSTMP1-4564                 PIC X(24).
                 05 WS-TYP-LST-ACT-0044          PIC X(01).
                       88 INSERT-PROCESS             VALUE "A".
                       88 DELETE-PROCESS             VALUE "D".
                 05 WS-CAGE-CD-9250                    PIC X(05).
                 05 WS-APP-TYP-9262                     PIC X(02).


Notice the 'A' and 'B'-areas - the '05'-level is inside the 'B'-area.   The level-numbers are two digits.


Mvh.

Geir Kildal




"Weatherly, Howard" <hweatherly@dlis.dla.mil>
Sent by: owner-cobol400-l@midrange.com

14.05.01 21:20
Please respond to COBOL400-L

       
        To:        "COBOL Midrange (E-mail)" <COBOL400-L@midrange.com>
        cc:        
        Subject:        Strange problem with linkage variables!





I am working on a program that receives data through the linkage section, only problem is that the first field can not be referenced!

Doing a prompted call and entering: '2001-05-05-06.45.20.402800A15992CD' in the parm field results in the field WS-TMSTMP1-4564 producing the message "POINTER NOT SET FOR REFERENCED LOCATION".

This is strange because I changed the code (see below) to move the linkage variable (LS-NEW-RECORD) to working storage (WS-NEW-RECORD). If I prompt (Interactive debugger) on LS-NEW-RECORD, the data appears as you would expect it. If however you look at WS-NEW-RECORD after the move, all fields except WS-TMSTMP1-4564 are available.

Is there something about the format of timestamp data that is causing me grief here??

                                                      
   1 WS-NEW-RECORD.                                   
     2 WS-TMSTMP1-4564        Pic  X(26).             
     2 WS-TYP-LST-ACT-0044    Pic  X(01).             
       88 INSERT-PROCESS                    VALUE "A".
       88 DELETE-PROCESS                    VALUE "D".
     2 WS-CAGE-CD-9250        Pic  X(05).             
     2 WS-APP-TYP-9262        Pic  X(02).             

  Linkage Section.                        
   1 LS-NEW-RECORD            Pic  X(34). 
                                          
 Procedure Division                       
     Using LS-NEW-RECORD                  
     .                                    
  0000-MAIN SECTION.                      
   0000-Begin.                            
                                          
     Move LS-NEW-RECORD to WS-NEW-RECORD  
                     

Howard Weatherly

(616)961-4324

hweatherly@dlis.dla.mil        
howard.weatherly@ctg.com

 <<...OLE_Obj...>>  <<...OLE_Obj...>>  <<...OLE_Obj...>>




 <<Weatherly, Howard.vcf>>



Weatherly, Howard.vcf


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.