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



Kevin,

It's been a while, but I believe this can be accomplished by specifying *YES 
for Secure Loc on the remote configuration list.

  From 720:
  WRKCFGL
  If QAPPNRMT exists, type 2
    If entry for 620 exists, change Secure Loc from *NO (default) to *YES
    If no entry for 620, add entry - be sure to specify *YES for Secure Loc
  If no QAPPNRMT, CRTCGL  TYPE(*APPNRMT)
    Add entry for 620 - be sure to specify *YES for Secure Loc

The profile and password on both systems has to match.  Also, be sure to 
specify RMTUSER(*CURRENT)  RMTPWD(*CURRENT) on the STRPASTHR screen.

Another way to accomplish this (not recommended, but possible), is to store the 
profile and password in a file or data area, then use a CL to retrieve the 
information.  On the STRPASTHR command, include RMTUSER(&user)  RMTPWD(&pwd)

And a final way that I can think of (again, not recommended) is to hardcode the 
profile and password in the CL.  On the STRPASTHR command, include 
RMTUSER(UserProfile), RMTPWD(CurrentPwd).

Todd Kidwell (Netstar)
AS/400 System Administrator
(313) 224-0578

+---
| 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
+---

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.