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



I guess I?m losing it. I?m using multiple files in a clle program for the
first time and also have a subroutine in it (for the first time). The
subroutine code appears below:

subr SltRcpOpt
chgvar &NoValidOpt 0 /* off is good! */
opndbf RcpCdeP1 option(*inp) opnid(pf)
monmsg cpf4174
posdbf pf *start
ReadNxt: rcvf opnid(pf)
monmsg cpf0864 exec(goto NoMatch) /* eof */
if (&pf_RcpCde = &SltOpt) then(rtnsubr +
rtnval(&NoValidOpt))
goto ReadNxt
NoMatch: chgvar &NoValidOpt 1
clof pf
endsubr rtnval(&NoValidOpt)

All this subroutine does is validates a user-entered option and returns an
integer value. My problem is with the posdbf command. It just does not
seem to be repositioning the pointer to the bof (this sub can be executed
multiple times within the program). Using debug view in iWDSC confirms
this. In addition, when the clof command executes and an opndbf
successfully re-executes, the file pointer is still not repositioned. The
job log doesn?t indicate anything unusual happening. Is there something
going on behind the scenes (ala ILE) since I?ve never had a problem with the
posdbf in an OPM program.



Buzz Fenner
Systems Analyst/Network Administrator
870.930.3374
mailto:bfenner@xxxxxxxxxxxxxxxx <mailto:bfenner@xxxxxxxxxxxxxxxx>




--
PRIVACY WARNING: For auditing purposes, a copy of this message has been
saved in a permanent database.

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.