We have a number of these type instructions in our programs. Another example is ACCOUNT=FIELD(OCONV(0,"U50BB")," ",2).
Is there something in the docs that describes what they are and what they do?
We have a number of these type instructions in our programs. Another example is ACCOUNT=FIELD(OCONV(0,"U50BB")," ",2).
Is there something in the docs that describes what they are and what they do?
We have a number of these type instructions in our programs. Another example is ACCOUNT=FIELD(OCONV(0,"U50BB")," ",2).
Is there something in the docs that describes what they are and what they do?
It's called a user exit. It returns the port number and account . It's the same as the WHO command at TCL. There's a section in Sisk's Pick Pocket Guide that documents some of them. They're either obsolete or there are better ways of doing them so it's not something I'd worry about.
We have a number of these type instructions in our programs. Another example is ACCOUNT=FIELD(OCONV(0,"U50BB")," ",2).
Is there something in the docs that describes what they are and what they do?
Nelson,
I believe someone wrote their own user exit for you solution.
Check your catalog space for 0223.
This should point you to the object code, and hopefully you have the source.
Nelson,
I believe someone wrote their own user exit for you solution.
Check your catalog space for 0223.
This should point you to the object code, and hopefully you have the source.
I took advantage of the necessary "U" to write an UPARROW conversion code, that I- & O-CONVs text into string like you see in ED's "^" uparrow mode; i.e. showing tab as ^009, etc. I can put UPARROW in <3> of a dictionary's D- or I-descriptor.
It's nice, but as bit hokey because cataloged as $PARROW. (Ideal-style cataloging in catdir. Pick users may not know this.)
Writing our own conversion codes is actually a nice idea that I wish UV would incorporate more formally into the product. It would be good for company-specific, account-specific, application-specific conversions.
The use would be mainly for in dictionaries, not programs. Without such, you need 2 dict items, one with the raw data, the 2nd an i-descriptor that calls a subroutine that transforms the string.
As it is, it is just an accommodation to for Pick users to help them convert to UV.
Nelson,
I believe someone wrote their own user exit for you solution.
Check your catalog space for 0223.
This should point you to the object code, and hopefully you have the source.
Thanks Mike,
This appears in hundreds of our programs. In a program file supplied by the authors of our ERP, it shows the following:
SUBROUTINE U0223(ANS,STATUS,DATA,TYPE)
ANS=''
RETURN
END
I have reached out to the authors to try to get a reason for this user exit.
Thanks for the assistance with the Dick Tracy stuff :-)
Nelson
Thanks Mike,
This appears in hundreds of our programs. In a program file supplied by the authors of our ERP, it shows the following:
SUBROUTINE U0223(ANS,STATUS,DATA,TYPE)
ANS=''
RETURN
END
I have reached out to the authors to try to get a reason for this user exit.
Thanks for the assistance with the Dick Tracy stuff :-)
Nelson
If I were to hazard a guess, the purpose is to set the value of STATUS() to 0, which is to what the status variable is assigned when the function returns.
By the way, in PI/open flavor (and, perhaps, Prime INFORMATION flavor), if a user exit has any characters past Uxxxx, e.g., Uxxxxyyyy, $xxxx is called and the user exit is passed in status,. e.g.:
function uxxxx(status, value, type)
branch = status[6, len(status)]
result = ''
status = 0
if type then
* Process ICONV()
end else
* Process OCONV()
end
return (result)
end
Henry
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
