Re: Getting rid of abandoned *SVRSTG objects that won't go away

[rob@xxxxxxxxx]

I have the following:
WRKNWSD
CITRIX1 
CITRIX2 
CITRIX4 
GDSBAAN1
GDSEDI1 
GDSNT1 
GDSSQL 
HELPSERV
HQLINUX 
With the last being a guested linux partition.
They are all up and running.
WRKOBJ *ALL/*ALL *SVRSTG only shows:
Object      Type      Library
QVNISYS1    *SVRSTG   QNTAP 
, which does not shows up in WRKNWSSTG.  What does show up is:
Name        Server
CITRIX11    CITRIX1
CITRIX12    CITRIX1
CITRIX13    CITRIX1
CITRIX21    CITRIX2
CITRIX22    CITRIX2
CITRIX23    CITRIX2
CITRIX41    CITRIX4
CITRIX42    CITRIX4
CITRIX43    CITRIX4
GDSBAAN11   GDSBAAN1
GDSBAAN12   GDSBAAN1
GDSEDI1     GDSEDI1 
GDSEDI11    GDSEDI1 
GDSEDI12    GDSEDI1 
GDSEDI13    GDSEDI1 
GDSNT11     GDSNT1 
GDSNT12     GDSNT1 
GDSNT3      GDSNT1 
GDSNT4      GDSNT1
GDSNT5      GDSNT1
GDSNT6      GDSNT1
GDSNT7      GDSNT1
GDSNT8      GDSNT1
GDSNT9      GDSNT1
GDSSQL1     GDSSQL
GDSSQL2     GDSSQL
GDSSQL3     GDSSQL
HELPSERV1   HELPSERV
HELPSERV2   HELPSERV
HELPSERV4   HELPSERV
HQLINUX     HQLINUX 

I wonder if all of these were created, or recreated, after V4R5?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Pete Helgren <Pete@xxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/25/2005 11:54 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Getting rid of abandoned *SVRSTG objects that won't go away






Interesting.  My 170 with IPCS has the following:

WRKNWSSTG:
            Percent 
Name        Used     Size   Server   Drive Format Access    ASP
 
DISK2GB1       18     2048  MICNTSVR   3   *NTFS  *UPDATE    1

If I do DSPOBJD *ALL/*ALL *SVRSTG

then I see the following:

Library:   QFPINT

 QFPBSYS1    17833984
 QFPBSYS2    69214208
 QFPBSYS3    37756928
 QFPBSYS4    10493952
 QFPBWPC1    14430208
 QFPBWPJ1    28262400
 QFPBWPK1    18882560
 QFPBWPT1    16781312

Library:   QNTAP
QVNISYS1    10493952

Library:   QUSRSYS
MICNTSVR1     10493952
MICNTSVR2    419450880
MICNTSVR3   1055952896


The last three make sense because they correspond to the C:,D: and F: 
drives on the IPCS.  Why the first  two objects  (MICNTSVR1/MICNTSVR2) 
don't show up in WRKNWSSTG is a bit of a mystery.

Anyway, sounds like something is buggered in the installation.  Are the 
LPP's still installed?

Pete Helgren

 
James H H Lampert wrote:

> Pete Helgren <Pete@xxxxxxxxxx> wrote:
>
>> Don't know if you got my earlier post but the *SVRSTG objects I had 
>> in QUSRSYS were created using the CRTNWSSTG command and can be 
>> deleted if you use WRKNWSSTG, unlink them, then delete them.  Don't 
>> know if you tried that and couldn't or not.
>
>
>
> Here's what I get, doing a DSPOBJD *ALL/*ALL *SVRSTG
>
> In QUSRSYS, I get:
> WINTOUCH1    with a size of 11799552
> WINTOUCH3    with a size of 38800384
>
> and in QXZ1, I get:
> QFPHSYS1     with a size of 11799552
> QFPHSYS2     with a size of 46664704
> QFPHSYS3     with a size of 38800384
>
> That's a total of 141M, a not-insignificant fraction of the total disk 
> space on the box.
>
> If I do a WRKNWSD or a WRKNWSSTG, I get a NWSD called WINTOUCH (listed 
> as "inactive"), but no storage is associated with it. If I try to do a 
> DLTNWSSTG on any of the objects named above, I get a "NOT FOUND" 
> error. And if I try to do an IFS DLT on them, I get a message about 
> the file system not supporting the operation. (I think I somehow did 
> something out of sequence, some years ago, when I was trying to cram 
> the entire system onto its one remaining drive. The docs on how to get 
> rid of a *SVRSTG appear to be practically nonexistent.)
>
> -- 
> JHHL

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