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


  1.  Home
  2. MIDRANGE-L
  3. January 2015

Re: remote 520 questions (more)

The cpf9190 error is sent when your password to the remote system expires. This is usually when the password on the remote system has expired or was changed.

To set it up use command adds route. The server must be QDDMSERVER all in upper case. You do need to re-enter the user profile local and remote. The password is for the remote system.

Addsvraute is done once for each user. When it expires or changes, use chgsvraute to enter the new remote password.

Sent from my iPad

On Jan 9, 2015, at 3:31 PM, John McKee <jmmckee@xxxxxxxxxxxxxx> wrote:

Rob, fantastic as always. On local system, there was an entry for the
specific server name of the remote system. I added DDMSERVER and my local
duplicate user profile from remote system. Works great.

Had to enclose DDMSERVER in quotes to get it in upper case.

The link you sent was most helpful.

Makes things easier, for sure.

John McKee

On Fri, Jan 9, 2015 at 1:39 PM, <rob@xxxxxxxxx> wrote:

Perhaps it is a combination of:
QRETSVRSEC
CHGDDMTCPA
DSPSVRAUTE

See also:

http://www.ibmsystemsmag.com/ibmi/tipstechniques/systemsmanagement/BRMS-Network-for-Secured-Connection/

Oddly there is no WRKSVRAUTE


For me, here:
QRETSVRSEC = '1'
CHGDDMTCPA AUTOSTART(*YES) PWDRQD(*VLDONLY)
DSPSVRAUTE:
User profile . . . . . . . . . : ROB
User Password
Server ID Stored
GDI ROB *YES

GDIHQ ROB *YES

GDIHQ1 ROB *YES

GDIHQ2 ROB *YES

GDISYS ROB *YES

GDISYS1 ROB *YES

GDISYS2 ROB *YES

GDWEB ROB *YES

GDWEB2 ROB *YES

GDWEB3 ROB *YES

MAILTWO ROB *YES

MAIL1 ROB *YES

MAIL3 ROB *YES
QDDMSERVER ROB *YES
RACK1HST ROB *YES
RACK2HST ROB *YES
RACK3HST ROB *YES



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/09/2015 02:17 PM
Subject: Re: remote 520 questions (more)
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Both local and remote have QRETSVRSEC = '1'

Not changed by me or anybody else that I know of in last few months.

Interesting that you managed to get the error I have just by changing the
value to zero and I get it with value '1'.

Local QSECURITY = 40. remote QSECURITY = 30 I have no idea why local
security at 40 would negatively effect connecting to remote at 30.



John McKee

On Fri, Jan 9, 2015 at 12:28 PM, <rob@xxxxxxxxx> wrote:

Good idea.
WRKSYSVAL *SEC
Especially QRETSVRSEC
Mine are set to 1.

CRTDDMF FILE(QTEMP/RCO) RMTFILE(ERPLXF/RCO) RMTLOCNAME(gdisys *IP)
dsppfm qtemp/rco
Database connection started over TCP/IP.
DDM object RCO in QTEMP uses remote object ERPLXF/RCO.
Works good.

CHGSYSVAL SYSVAL(QRETSVRSEC) VALUE('0')
signoff/on
CRTDDMF FILE(QTEMP/RCO) RMTFILE(ERPLXF/RCO) RMTLOCNAME(gdisys *IP)
dsppfm qtemp/rco

CPF9190
Message . . . . : Authorization failure on DRDA/DDM TCP/IP connection
attempt.
Cause . . . . . : A connection attempt failed with reason code 17.

Sound familiar?

CHGSYSVAL SYSVAL(QRETSVRSEC) VALUE('1')
no signoff/on
dsppfm qtemp/rco
Database connection started over TCP/IP.
DDM object RCO in QTEMP uses remote object ERPLXF/RCO.

Worked great!


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 01/09/2015 01:16 PM
Subject: RE: remote 520 questions (more)
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Check out the security system values to be sure they are set right
(Assuming
you did not check those yet)

Beyond that we'd have to see logs to see what the precise error message
is.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
John
McKee
Sent: Friday, January 09, 2015 11:56 AM
To: Midrange Systems Technical Discussion
Subject: Re: remote 520 questions (more)

I am assuming, based on only what I can see from a distance, that only
"easy" answer would be to replace multiple 4326 drives (four remain)
with
4327s, if additional storage was needed. That wouldn't be my job
either.
Just trying to be able to answer questions I know will be coming.

I looked at DDM. Both sides are configured the same. Same user profile
on
both systems. But, I don't know if some service part of DDM "there"
lacks
authority to files that I only have due to a group profile connection.

John McKee

On Fri, Jan 9, 2015 at 11:11 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

1) One drive out of a RAID set (V5R3) no problem other than the
system is no longer protected. Another drive fails goodbye partition.
Reload time.
Since the Cache is out it will take some "major minutes" to do. (read
many
hours)
2) IBM does not have an easy answer; the OEM product route is the
best, call Brad.
3) Unknown but a bit doubtful. My guess is you'll need to add some
storage, that's the bad news. Good news is for that usage it will be
cheap (assuming the HSL loop adapter is there)
4) I think Rob's earlier answer to this was accurate. It's most
likely the DDM attributes that are causing the problem, or the user
profile/password combination does not exist on both sides.


--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
John McKee
Sent: Friday, January 09, 2015 10:37 AM
To: Midrange Systems Technical Discussion
Subject: remote 520 questions (more)

I was asked mor questions.

As part of the (in)famous "decommissiong", we continue to find issues.
For example, I am looking at an output that has 171423 files. There
are other queues with a large number as well, but probably not as
many. Cache battery is gone.

Since we recently had cache battery and hard drive replaced on local
system, I feel confident (maybe foolishly?) that this isn't an issue,
but I was asked. If a remote drive craps out - it is in a RAID set,
is there any potential data loss? They are keeping things in output
queues because there is no alternative.

They need to keep the content, which brings up the related question,
and I am thinking no easy answer here. Remote is v5r3. Can the spool
files be converted to PDF? I am cringing at the thought of doing this
for 171423 or even 11,736 files. But, I have to ask. Does SPOOLTOOL
have this capability?

Due to large outques and I don't know how much actual junk, if
SPOOLTOOLS could do conversion to PDF (again, on v5r3 system), could
it be installed without pushing Dasd over the edge? System is at
88.5142
of 317.1G.

I created a user profile on local 520 (v5r4) with same user name and
password as my profile ob the remote system. Still could not open a
DDM file. Same error and reason code - 17. Maybe there is an exit
program involved, but command to look at exit programs has slipped
away from active memory. Maybe it is just file authority. My login
is tied to a group profile so when I sign on, I have needed authority
to access files. Maybe whatever job provides DDM service needs that
authority - if so, what profile is that?

I deeply appreciate your patience and assistance. This whole process
is rapidly approaching the looney stage.

John McKee
--
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.


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


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


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


--
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.
--
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 thread ...
Replies:
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.