Re: Embedded SQL problem

[santoshp@xxxxxxxxxxxxxxxxx]

John..
do this..

       01 VendorRecordWS.
          05 VendR.
          10 VENDORID              PIC X(6).
          10 VENDORNAME            PIC X(30).
          10 ADDRESSLINE1          PIC X(30).
      01 WS-INS-VENDOR             PIC X(66).
              :  etc. for every field in the file
      *    Write VendorRecord
      INITIAlize WS-INS-VENDOR
      MOVE VendorRecordsWS to WS-INS-VENDOR
           Exec SQL
                Insert into VendP
                Values( :WS-INS-VENDOR)
         End-exec.


This solution is self explanatory..
Santosh.


Message: 6
From: "Jon Paris" <Jon.Paris@Partner400.com>
To: "Midrange-l" <midrange-l@midrange.com>
Subject: Embedded SQL problem
Date: Tue, 30 Jul 2002 18:41:54 -0400
Reply-To: midrange-l@midrange.com

This may belong on the COBOL list but I doubt the problem is COBOL
specific.

This code (extracted from a larger program) will not compile - insisting
that VendR "not defined or not usable."  The VENDR structure is compiler
created (or at least in the full program it was) and has all fields in the
correct sequence.


       01 VendorRecordWS.
          05 VendR.
          10 VENDORID              PIC X(6).
          10 VENDORNAME            PIC X(30).
          10 ADDRESSLINE1          PIC X(30).
              :  etc. for every field in the file
      *    Write VendorRecord
           Exec SQL
                Insert into VendP
                Values( :VendR)
           End-exec.

I've tried qualifying the name (shouldn't be needed) and everything else I
can think of but ....

Anybody got any ideas?

Jon Paris
Partner400

Signature......................

e- mail at :  santoshp@lot.tatasteel.com
FPC-IS, ITS, Tata Steel.
Jamshedpur, India.
Tel : 142134 (O)



                            DISCLAIMER
Information contained and transmitted by this e-mail is confidential and
proprietary to Tata Steel Ltd. and is intended for use only by the
addressee. If you are not the intended recipient , you are notified that
any dissemination or copying of this e-mail is strictly prohibited and you
are requested to delete this e-mail immediately and notify the originator.
Tata Steel does not enter into any binding agreement with any party by
e-mail. Any views expressed by an individual do not necessarily reflect the
view of Tata Steel. Tata Steel is not responsible for the consequences of
any actions taken on the basis of information provided.
While this e-mail has been checked for all known viruses the addressee
should also scan for viruses.
To know more about Tata Steel please visit www.tatasteel.com