opdesc doesnt work?

Scott,

<<Actually, my most recent OS/400 upgrade broke several of my applications.
<<(Operational Descriptors just dont work on V4R5!  I had to change them to
<<not use opdesc.  Several other apps didnt work, including the OS/400
<<telnet server, until I installed PTFs.)

We use the opdesc keyword in our snderrmsg procedure which is used
throughout our application to send error messages to the screen. We have
not experienced any problem since upgrading to V4R5. Granted, we are only
using it to get the length of the message data passed to the procedure.


I'm very interested in this since we have a lot of accounts running our
software that will eventually upgrade to v4r5 also.  What problems are you
experiencing with operational descriptors? Are you sure its v4r5 related?
Are you using it to extract information other than the length of a
parameter?



Ron Hawkins

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---