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



OK, I RTFM'ed and it didn't help much. I must be really dense.

So, let's say I created two files, INFDS_DSPF and INFDS_POST, with the two
different field layouts.

In my workstation file spec, I use the keyword INFDS(DSPF_IO_Info).

Then, I create two data structures (DSPF_IO_Info and DSPF_Attribute) that
bring in the two external file layouts.

DSPF_IO_Info works like it always did, supplying information after each file
op.

Then on the POST operation, if I understand what you are saying below, what
I want to do is:
        1.)  put the Device name in factor 1,
        2.)  leave factor 2 blank, and
        3.)  put the alternate data structure name, "DSPF_Attribute", in the
result field.

Is that correct?

However, the way I read the manual, if I leave factor 2 blank, I "must
specify the data structure name that has been used in the INFDS keyword for
the file specification in the result field". Doesn't sound like it's
optional. It's only optional if I do specify the workstation file name in
factor 2.  In that case, it will use the data structure name specified on
the INFDS keyword.  Either way, I don't seem to have the choice of
specifying the second data structure name, DSPF_Attribute.

What am I missing here? How do tell the POST operation to put the attribute
data into the attribute data structure?


> Ahhhh.  Did you read up on the POST operation code?  Result field is an
> optional data structure.  In your case, I'd leave the standard INFDS alone
> and create a new external file for the POST layout and specify that DS as
> the result field.  You'll want to carefully read this section, because the
> mere presence of POST _even if it never executes_ can change the way the
> standard INFDS operates.
>
>   --buck
>
>


************************************************************************************************************************************************************************************************************
This message originates from Lincare Holdings Inc. It contains information 
which maybe confidential or privileged and is intended only for the individual 
or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the 
contents of this message.
All personal messages express views solely of the sender, which are not to be 
attributed to Lincare Holdings Inc., and may not be copied or distributed 
without this disclaimer.
If you received this message in error, please notify us immediately at 
MailAdmin@lincare.com or (800) 284-2006.
************************************************************************************************************************************************************************************************************



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.