I cannot speak for non HDS disk, the engineers could do a low level format.

Allan

________________________________

From: owner-vse-l@Lehigh.EDU on behalf of Hans Rempel
Sent: Fri 26/01/2007 4:18 p.m.
To: VSE Discussion List
Subject: RE: Destroying Data on Old Disks

I've always wondered how effective this would be on RVA where volumes are all virtual. Writing all H will be highly compressed and not overwrite the data on the 3.5 inch drives supporting the virtual volumes. I realize the data on the RVA backend drive is somehow compressed and striped over a number of drives but can a PC program not scan the individual drives and pick up some data that may not be comprised?

Hans

________________________________

From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of Mike Rice
Sent: January 25, 2007 3:30 PM
To: VSE Discussion List
Subject: Re: Destroying Data on Old Disks

Thanks to all who responded! CLRDK is working great!

Mike

http://groups.google.com/group/bit.listserv.vse-l/browse_thread/thread/8617b9f935c5ffde/cd1f6e555b6d934d...#cd1f6e555b6d934d

Tony,

I apologize for earlier not actually answering your original question.
I cannot answer for VM since we are a native shop but as for VSE, a
manual change will work just fine. Unlike our counterparts in the world
of Windows (and possibly other client/server operating systems), the
developers of VSE were wise enough to know better than to place those
controls 'inside' the operating system code.

Admittedly, the 'wisdom' I speak about may just be that the VSE
developers were too busy giving us a stable, durable, efficient
operating system and leaving these neat little 'toys' to the other guys.
Thank You, Boeblingen!

Jim Kovac

Note: The opinions expressed here are those of the writer and do not
neccasariliy reflect the opinions of United Medical Resources, Inc.
(Sorry, I have to say that)

I did it the hard way. My VSE 2.6.3 system would not come up due to
maintenance considerations. The install of VSE 3.1.2 was painless, even
for a MVS person who has touched VSE 20+ years ago.

-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of dabbate@courts.state.va.us
Sent: Friday, January 19, 2007 9:14 AM
To: VSE Discussion List
Subject: To FSU or not to FSU

I am getting ready to upgrade my VSE 2.6.3 system to zVSE3.1.2. I would
like to get there via FSU vs a full install. However, we haven't quite
adhered 100%% to IBM's guidelines on where to place things...

I don't think any of that is going to be a problem, except for maybe the
CSD. You will need to do an upgrade on the groups in the CSD to pick up the
new definitions (there should be info in the various release guides). Or
just copy the updated groups from the standard CSD to your own.

On 1/19/07, dabbate@courts.state.va.us wrote:

Don,

We have some of the same conditions that you described. However, when
I went from VSE/ESA 2.5 to VSE/ESA 2.7.3 I chose to do a full install.
The reason was new placements of files, new allocations for Libraries
and VSAM Catalogs, etc.

Dave

Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
David.Stuart@ventura.org

I am getting ready to upgrade my VSE 2.6.3 system to zVSE3.1.2. I
would
like to get there via FSU vs a full install. However, we haven't
quite
adhered...

Which manual contains the error messages produced by the 3494 VTS to
the operating system and EPIC?

I am installing EPIC under z/VSE 3.2.1 and I am getting an "EPT590W IBM
ACL CMOUNT ERROR RC=0039 REASON=6100 " message.

I cannot find the doc for the VTS that shows me what the RC=0039 and
REASON=6100 means.

Stephen ...

--
Kevin Corkery
Independent Consultant
Voorhees, New Jersey

-------------- Original message ----------------------
From: Stephen Frazier

Is it possible to set up a job so that it is processed by both AUTOLPR and AUTOEMAIL?
I am running CSI TCP/IP 1.5E. I have set up POWER queue "T" for AUTOLPR and POWER queue "E" for
AUTOEMAIL. I have a job that needs to have a LST card that goes to both queues. I would like to be
able to have a AUTOEMAIL script that after it sends the email it will put the listing in the AUTOLPR
queue or a AUTOLPR script that after it prints the listing will put it in the AUTOEMAIL queue.

--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: (405) 425-2549
Fax: (405) 425-2554
Pager: (405) 690-1828
email: stevef%%doc.state.ok.us

Frank,

I can't tell you exactly when this occurred. The best I can tel and if
memory serves the processor info was added, removed then re-added. Here's code
I've been using on a 3.1.1 system to extract the processor info. I seem to
recall asking Axel (before he retired and subsequently passed away) how this info
is obtained but got no answer. The following may not be what you want but
it's all I got/know:

LA R1,SETIJBAR LOAD ADDRESS OF $IJBAR TO REG 1.
CDLOAD (R1),RETPNF=YES , ISSUE CDLOAD.
LTR RF,RF WAS THERE A CDLOAD ERROR.
BZ SETCMD8L_0 NO-BRANCH...

I can't tell when the $IJBAR module changed. I'm at 3.1.2 and the beginning of it has:

05D00700 47F0D058 00413ED8 F5F6F8F6 *.}...0}....Q5686*
60C3C6F7 404DC35D 40C3D6D7 E8D9C9C7 *-CF7 (C) COPYRIG*
C8E340C9 C2D440C3 D6D9D74B 40F1F9F7 *HT IBM CORP. 197*
F96B40F2 F0F0F540 C9D1C2C1...