|
AAAAAAAAAAAAAAAAAAARGH! OK....Sorry to have wasted the List's time with this. Turns out that someone, in the last 24 hours, has changed the QRMTSIGN system value back to *FRCSIGNON without telling me. I'd had it set to *SAMEPRF for over a month now but someone changed it on me, I guess it was in an effort to "help me" with my current task, and I didn't even think to check that. YEESH!!!!!! FYI: When I change the User Profile using the QWSETP API to a new user, I can do a transparent TELNET to a remote system using the new User profile (and with the remote system set to *SAMEPRF for QRMTSIGN System Value). This reminds me of my father-in-law, who, last weekend, was trying to help me take the mower deck off of my garden tractor. I kept telling him that I had it under control and that I do it by myself all the time but he kept insisting on helping me to the point that I was telling him to "Please don't help me with this!" because he'd lift when I wasn't expecting it and pinch my fingers between metal and he'd pull when I thought he was going to push and I ended up with bloody hands and bruised knuckles. Well intentioned, uninvited help can sometime be more trouble than it's worth. Shannon O'Donnell ----- Original Message ----- From: <rob@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, May 28, 2003 10:39 AM Subject: Re: Refresh Job after using the Set Profile Handle API and TELNET > You've considered replicating the data and rejected that. > > You've considered TELNET and are pursuing that. > > Have you considered either DDM, or the SQL CONNECT TO instead? > > Rob Berendt > -- > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." > Benjamin Franklin > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.