Hi Team,

We are facing file mounting issue with RDT mainframe server. Please find the attachment of screen shot for your reference. Kindly help us with your inputs.

Thanks,

Basavaraj.A.S

Please do help us with your inputs. Thanks in advance.

Note : We did IPL and even we tried mounting the specified file but nothing has worked out for us.

It seems to say that the disk called S1BBN is offline. IS it available? Is it in the devmap? Can it be varied online?

Br Michael Erichsen

Xact Consulting

Hi,

S1BBN1 is not in the devmap. The IPL was successful earlier with the same devmap. But we shifted the server to a new place and then we got this problem with S1BBN1 offline.

We tried Varying, but it said the logical path is missing. So we did try Vary Path as well, it is rejected with the following error:

IEE384I VARY REJECTED, UCB FOR DEVICE 0A81 NOT CONNECTED.

Thanks,

Basavaraj.A.S

Hi

It needs to be in your devmap, unless you have added it dynamically.

Br Michael

Hi Sir,

From the attached screens shot we can see that code is commented for S1BBN1. So we are assuming that S1BBN1 is picking up dynamically. Please do let us know how to fix it.

Thanks,

Basavaraj.A.S

Hi

Dynamic mounts are not happening "behind your back", but only as a conscious action.

If you want to use z/OS MF you probably need to

1) check that the disks in question are actually present where the outcommented devmnaps entries show them

2) uncomment the devmap entries

3) Re-ipl

4) if needed do VARY ACT on the console for 0A81, 0A83 and 0A84

Alternatively you can decide not to activate z/OS MF. Then you should keep them commented out and also comment the mount statements out for IZU210.SIZUZFS in one of your parmlib BPXPRM* members.

Br Michael Erichsen,

Xact Consulting

Thank you sir for your detailed inputs. But as shared in the screenshots,the disks are NOT present.

So what will be the impact of commenting out mount zosmf? Please do let us know.

Thanks,

Basavaraj.A.S

Hi

I assume that you are running z/OS 2.1 from the "S1" prefix to your disks. ZOSMF is not mandatory at that version og z/OS, so you don't need it.

The actual message is written by the Health Checker (HZSPROC). It is possible that you have had the mount error all along, but that it only has surfaced now by the Health Checker message.

I get a lot of messages from the health checker that I want to ignore. They are typically different from version to version of ADCD, so I first fix real inconsistencies like missing mounts and APF list errors. Then I change the parmlib HZSPRMxx member and activate it to suppress unwanted messages.

Br MIchael Erichsen

Xact Consulting

Your RD&T and z/OS systems will never see this disk, even if the file exists as you have it commented out in your DEVMAP. If you need this disk and the filesystems on it then you must uncomment it and then restart RD&T and your z/OS system.

Sebastian