×
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.
Scott Klement wrote:
I suggest coding it to the v5r1 level, and tell customers that the
minimum release for SSL support is v5r1. You'd be doing them a
disservice, quite frankly, to try to make SSL work earlier than that.
If for no other reason than because the SSL standards available back
then aren't considered secure anymore today.
Dear Scott:
Sorry if I seem a bit sarcastic. It's not you; it's the way the whole
day has been going, starting with learning last night that one of the
cats is dying, of kidney failure, and has probably already been
euthanized by now.
At any rate, I don't mind one bit making the "secured link" part only
available on V6R1 (so long as I can make the application work with both
V4 and V6 versions of the service program). Assuming I can figure out
that part at all (and lately, I've been seeing lots of things to make me
want to retire early, and get a job driving an ice resurfacer).
In fact, the only thing I've seen all week that has qualified as "fun"
has been my discovery that any user can "give" IFS objects to his or her
primary group profile (via either CL CHGOWN or the chown() and fchown()
API calls), without restriction.
All I care about at this point is un-/free-ing the syntax, so I can get
the existing functionality to compile on the V4 box.
And alas, we have development tools for V4 and V6, but not V5. The
closest thing we have on our V5 box to a development tool is a REXX
script that allows us to make an OPM program compatible with both V5 and
V6, and still yank the observability.
--
JHHL
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.
midrange.com
