Discussion:
RMTCMD under windows xp question
(too old to reply)
Brad Holman
2005-02-02 20:20:42 UTC
Permalink
I have ported several batch files from a pc running windows 98 se to a pc
running windows xp. One of these batch files invokes several AS/400
programs using the RMTCMD command. Running on the new pc, the user is
prompted to enter a username/password each time the RMTCMD command is
executed (about six times!). On the old pc, the user was only prompted
once, and apparently subsequent invocations used the previous
username/password. My assumpion is that the configuration of Client Access
on the old computer somehow cached the login information. Any help would be
appreciated.

Please post response to the newsgroup, responding to my email won't work...

thanks,
Brad Holman
Rex Moore
2005-02-02 20:24:02 UTC
Permalink
Did you check out the Incoming Remote Command tab on iSeries Access in the
windows control panel? You might find some settings there useful.
Post by Brad Holman
I have ported several batch files from a pc running windows 98 se to a pc
running windows xp. One of these batch files invokes several AS/400
programs using the RMTCMD command. Running on the new pc, the user is
prompted to enter a username/password each time the RMTCMD command is
executed (about six times!). On the old pc, the user was only prompted
once, and apparently subsequent invocations used the previous
username/password. My assumpion is that the configuration of Client Access
on the old computer somehow cached the login information. Any help would
be appreciated.
Please post response to the newsgroup, responding to my email won't work...
thanks,
Brad Holman
Brad Holman
2005-02-02 20:43:29 UTC
Permalink
I did, but under the version of Client Access I have, there is not facility
for adding remote users. I was also under the impression that tab was used
to control AS/400 access to a pc, not pc access to the AS400. At any rate,
there are just facilities for setting 'security options" and 'allow generic
security'.
I am running Version 5, mod level 0, service level SI11806...
Post by Rex Moore
Did you check out the Incoming Remote Command tab on iSeries Access in the
windows control panel? You might find some settings there useful.
Post by Brad Holman
I have ported several batch files from a pc running windows 98 se to a pc
running windows xp. One of these batch files invokes several AS/400
programs using the RMTCMD command. Running on the new pc, the user is
prompted to enter a username/password each time the RMTCMD command is
executed (about six times!). On the old pc, the user was only prompted
once, and apparently subsequent invocations used the previous
username/password. My assumpion is that the configuration of Client
Access on the old computer somehow cached the login information. Any help
would be appreciated.
Please post response to the newsgroup, responding to my email won't work...
thanks,
Brad Holman
Rex Moore
2005-02-02 21:20:31 UTC
Permalink
V5R3 of iSeries access in the control panel for incoming remote command in
XP has options cache security, generic security runs command as logged-on
user, allow generic security, etc...
Post by Brad Holman
I did, but under the version of Client Access I have, there is not facility
for adding remote users. I was also under the impression that tab was used
to control AS/400 access to a pc, not pc access to the AS400. At any rate,
there are just facilities for setting 'security options" and 'allow generic
security'.
I am running Version 5, mod level 0, service level SI11806...
Post by Rex Moore
Did you check out the Incoming Remote Command tab on iSeries Access in
the windows control panel? You might find some settings there useful.
Post by Brad Holman
I have ported several batch files from a pc running windows 98 se to a pc
running windows xp. One of these batch files invokes several AS/400
programs using the RMTCMD command. Running on the new pc, the user is
prompted to enter a username/password each time the RMTCMD command is
executed (about six times!). On the old pc, the user was only prompted
once, and apparently subsequent invocations used the previous
username/password. My assumpion is that the configuration of Client
Access on the old computer somehow cached the login information. Any
help would be appreciated.
Please post response to the newsgroup, responding to my email won't work...
thanks,
Brad Holman
Oogla D. Mok
2005-02-03 02:45:12 UTC
Permalink
Post by Rex Moore
V5R3 of iSeries access in the control panel for incoming remote
command in XP has options cache security, generic security runs
command as logged-on user, allow generic security, etc...
Post by Brad Holman
I did, but under the version of Client Access I have, there is not
facility for adding remote users. I was also under the impression
that tab was used to control AS/400 access to a pc, not pc access to
the AS400. At any rate, there are just facilities for setting
'security options" and 'allow generic security'.
I am running Version 5, mod level 0, service level SI11806...
Post by Rex Moore
Did you check out the Incoming Remote Command tab on iSeries Access
in the windows control panel? You might find some settings there
useful.
Post by Brad Holman
I have ported several batch files from a pc running windows 98 se to
a pc running windows xp. One of these batch files invokes several
AS/400 programs using the RMTCMD command. Running on the new pc,
the user is prompted to enter a username/password each time the
RMTCMD command is executed (about six times!). On the old pc, the
user was only prompted once, and apparently subsequent invocations
used the previous username/password. My assumpion is that the
configuration of Client Access on the old computer somehow cached
the login information. Any help would be appreciated.
Please post response to the newsgroup, responding to my email won't work...
thanks,
Brad Holman
As Brad pointed out, RMTCMD is *outgoing* remote command. The incoming
remote command settings aren't significant.

In this case, check the connection properties. In Operations Navigator
(iSeries Navigator on later releases), right click on the system and
select properties. On the connection tab there is a signon information
section. My guess is that "prompt every time" is selected. If the
user's Windows user ID and password are the same as their 400 profile
and password, try using the "use Windows user name..." option, if not,
use the "use default user ID..." option and plug in their 400 profile.
Brad Holman
2005-02-03 20:23:30 UTC
Permalink
I have noticed on the other pc (the one being replaced) that the Connection
tab under the "AS400 operations manager | (as400dnsname) | properties" menu
is set to "use default id, prompt as needed". This setting on the new pc is
"prompt every time". From reading the help file for signin information, I
believe setting this to "use default id, prompt as needed" on the new pc
will indeed fix my problem (I won't know until Monday, when this weekly
procedure is run again).

Many thanks to everyone for helping me fix this issue...
Brad Holman
Post by Oogla D. Mok
Post by Rex Moore
V5R3 of iSeries access in the control panel for incoming remote
command in XP has options cache security, generic security runs
command as logged-on user, allow generic security, etc...
Post by Brad Holman
I did, but under the version of Client Access I have, there is not
facility for adding remote users. I was also under the impression
that tab was used to control AS/400 access to a pc, not pc access to
the AS400. At any rate, there are just facilities for setting
'security options" and 'allow generic security'.
I am running Version 5, mod level 0, service level SI11806...
Post by Rex Moore
Did you check out the Incoming Remote Command tab on iSeries Access
in the windows control panel? You might find some settings there
useful.
Post by Brad Holman
I have ported several batch files from a pc running windows 98 se to
a pc running windows xp. One of these batch files invokes several
AS/400 programs using the RMTCMD command. Running on the new pc,
the user is prompted to enter a username/password each time the
RMTCMD command is executed (about six times!). On the old pc, the
user was only prompted once, and apparently subsequent invocations
used the previous username/password. My assumpion is that the
configuration of Client Access on the old computer somehow cached
the login information. Any help would be appreciated.
Please post response to the newsgroup, responding to my email won't work...
thanks,
Brad Holman
As Brad pointed out, RMTCMD is *outgoing* remote command. The incoming
remote command settings aren't significant.
In this case, check the connection properties. In Operations Navigator
(iSeries Navigator on later releases), right click on the system and
select properties. On the connection tab there is a signon information
section. My guess is that "prompt every time" is selected. If the
user's Windows user ID and password are the same as their 400 profile
and password, try using the "use Windows user name..." option, if not,
use the "use default user ID..." option and plug in their 400 profile.
Brad Holman
2005-02-15 13:35:01 UTC
Permalink
Changing this setting as described below did indeed fix my problem. Thanks
again to everyone for their help...
Brad
Post by Brad Holman
I have noticed on the other pc (the one being replaced) that the Connection
tab under the "AS400 operations manager | (as400dnsname) | properties" menu
is set to "use default id, prompt as needed". This setting on the new pc
is "prompt every time". From reading the help file for signin information,
I believe setting this to "use default id, prompt as needed" on the new pc
will indeed fix my problem (I won't know until Monday, when this weekly
procedure is run again).
Many thanks to everyone for helping me fix this issue...
Brad Holman
Post by Oogla D. Mok
Post by Rex Moore
V5R3 of iSeries access in the control panel for incoming remote
command in XP has options cache security, generic security runs
command as logged-on user, allow generic security, etc...
Post by Brad Holman
I did, but under the version of Client Access I have, there is not
facility for adding remote users. I was also under the impression
that tab was used to control AS/400 access to a pc, not pc access to
the AS400. At any rate, there are just facilities for setting
'security options" and 'allow generic security'.
I am running Version 5, mod level 0, service level SI11806...
Post by Rex Moore
Did you check out the Incoming Remote Command tab on iSeries Access
in the windows control panel? You might find some settings there
useful.
Post by Brad Holman
I have ported several batch files from a pc running windows 98 se to
a pc running windows xp. One of these batch files invokes several
AS/400 programs using the RMTCMD command. Running on the new pc,
the user is prompted to enter a username/password each time the
RMTCMD command is executed (about six times!). On the old pc, the
user was only prompted once, and apparently subsequent invocations
used the previous username/password. My assumpion is that the
configuration of Client Access on the old computer somehow cached
the login information. Any help would be appreciated.
Please post response to the newsgroup, responding to my email won't work...
thanks,
Brad Holman
As Brad pointed out, RMTCMD is *outgoing* remote command. The incoming
remote command settings aren't significant.
In this case, check the connection properties. In Operations Navigator
(iSeries Navigator on later releases), right click on the system and
select properties. On the connection tab there is a signon information
section. My guess is that "prompt every time" is selected. If the
user's Windows user ID and password are the same as their 400 profile
and password, try using the "use Windows user name..." option, if not,
use the "use default user ID..." option and plug in their 400 profile.
Murlock
2005-02-03 15:26:06 UTC
Permalink
Post by Brad Holman
I have ported several batch files from a pc running windows 98 se to a pc
running windows xp. One of these batch files invokes several AS/400
programs using the RMTCMD command. Running on the new pc, the user is
prompted to enter a username/password each time the RMTCMD command is
executed (about six times!). On the old pc, the user was only prompted
once, and apparently subsequent invocations used the previous
username/password. My assumpion is that the configuration of Client Access
on the old computer somehow cached the login information. Any help would be
appreciated.
Please post response to the newsgroup, responding to my email won't work...
thanks,
Brad Holman
You can use CWBLOGON to set the username / password before lauching your
RMRCMD


Cheers
Murlock
Loading...