Never, ever, link to a CMS minidisk MW unless you have been advised to do
so by a trained VM professional.
Doing so because you don’t know what else to do is a good way to destroy
the minidisk. The CMS minidisk file system doesn’t support multiple
concurrent writers. Even its support for some
Our zVM is a non ssi..I was able to get the MW mode by linking LNXADMIN.
Thanks for all the help
On Tue, 3 Sep, 2019, 9:10 AM Roberto Ibarra Magdaleno, <
roberto.ibar...@gmail.com> wrote:
> Then the problem origin is in the LNXADMIN user if it has the 191 minidisk
> RO from the LOGON. Could you
Then the problem origin is in the LNXADMIN user if it has the 191 minidisk
RO from the LOGON. Could you check/retrieve the user's directory and show
us? is there another user linking to it RW?
Regards.
Roberto.
El lun., 2 de sep. de 2019 a la(s) 23:21, Jake Anderson (
justmainfra...@gmail.com) es
So why are you logging in to the user to link its disk? If LNXADMIN has it
linked r/o then you should be good to go from the ftp client. I assume you are
using LNXADMIN's credentials when prompted by the ftp client. What do you see
once the login completes? If LNXADMIN has the 191 in r/o the the
I am connecting from z/VM to a ftp server (windows)
On Tue, 3 Sep, 2019, 8:17 AM Neale Ferguson, wrote:
> You don't. The FTPSERVE use will try to link LNXADMIN 191 and access it.
> If LNXADMIN has the disk r/o that will allow FTPSERVE to link it r/w. So
> get rid of the W disk - REL W(DET. Then
You don't. The FTPSERVE use will try to link LNXADMIN 191 and access it. If
LNXADMIN has the disk r/o that will allow FTPSERVE to link it r/w. So get rid
of the W disk - REL W(DET. Then go to the ftp client and try to connect as
LNXADMIN.
Original message
From: Jake Anderson
1st of all never go MW.
Secondly you've linked 191 as 999 but then accessed 191. 191 is still r/o. If
you're on LNXADMIN then LINK * 191 191 W. Then ACC 191 A (you could just use
ACC but if you're setup to use SFS you may not get what you're expecting).
Otherwise LINK LNXADMIN 191 99 W# ACC 999
I was able to access it as disk W as 999. But while ftping how do I route
to w ?
On Tue, 3 Sep, 2019, 7:52 AM Jake Anderson,
wrote:
> For some reason tried all the recommendation but still LNXADMIN gets R/O.
>
> I did
>
> Link LNXADMIN 191 999 mw
> 00: DASD 0999 link R/W; R/O BY LNXADMIN
> ACC 1
For some reason tried all the recommendation but still LNXADMIN gets R/O.
I did
Link LNXADMIN 191 999 mw
00: DASD 0999 link R/W; R/O BY LNXADMIN
ACC 191 a
DMSACC724I 191 Replaces A (191)
DMSACP723I A (191) R/O
On Mon, 2 Sep, 2019, 7:06 PM Mike Beer, wrote:
> Did you try
> LINK .. ... MW
> Inst
Did you try
LINK .. ... MW
Instead of W?
Should give you multiple write.
Best regards
Mike
-Ursprüngliche Nachricht-
Von: Linux on 390 Port Im Auftrag von Rob van der Heij
Gesendet: Monday, September 02, 2019 11:42
An: LINUX-390@VM.MARIST.EDU
Betreff: Re: Redhat build first time
On Mon
On Mon, 2 Sep 2019 at 06:30, Jake Anderson wrote:
Any clue how can I turn LNXADMIN into R/W ?
>
LINK W
ACCESS A
FTP ...
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu
11 matches
Mail list logo