× 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.


  • Subject: Re: Strange problem with linkage variables!
  • From: chandru <ganduri@xxxxxxxxx>
  • Date: Tue, 15 May 2001 21:13:06 -0700 (PDT)

Hi Howard,

In my opinion there is one way to overcome the
problem. Replace the group record in the Linkage
section with the exact structure as in Working storage
section and make elementary MOVES in place of the
Group move.

It sounds stupid but it works...see the example below:

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).  
  2 LS-TMSTMP1-4564        Pic  X(26).           
   
  2 LS-TYP-LST-ACT-0044    Pic  X(01).           
  2 LS-CAGE-CD-9250        Pic  X(05).           
  2 LS-APP-TYP-9262        Pic  X(02).           

PROCEDURE DIVISION.

MOVE LS-APP-TYP-9262 TO WS-APP-TYP-9262.
MOVE LS-CAGE-CD-9250 TO WS-CAGE-CD-9250.

So on so forth.....

thanks


--- "Weatherly, Howard" <hweatherly@dlis.dla.mil>
wrote:
> 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>> 
> 

> ATTACHMENT part 2 application/octet-stream
name=Weatherly, Howard.vcf



=====
Chandrasekhar G
TelNo: (off) - +91-40-3097505(extn:3375)
       (res) - +91-40-7171573
e-mail: ganduri@yahoo.com

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
+---
| This is the COBOL/400 Mailing List!
| To submit a new message, send your mail to COBOL400-L@midrange.com.
| To subscribe to this list send email to COBOL400-L-SUB@midrange.com.
| To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---END


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.