On Thu, 2 Apr 2009 15:05:13 -0700, Raymond Noal <raymond.n...@hds.com>
wrote:
>B-I-N-G-O !!!!
>
>James wins the cigar!
>
>On the MAINT virtual machine where everything worked as expected, there
>was a PROFPEEK XEDIT file on the 191 A-Disk. For the other two machines
>that were encountering the problem, they only had a PROFPEEK XEDIT on
>their 190 S-Disk. I copied the PROFPEEK XEDIT from MAINT to the other
>two virtual machines on their 191 A-Disk, and now they work as expected.
>
>So, is the PROFPEEK XEDIT on the 190 S-DISK in error? I've opened a PMR
>with IBM. Stay tuned - film at eleven!!
>
>Thanks to all who have responded so promptly.
>
>HITACHI
> DATA SYSTEMS
>Raymond E. Noal
>Senior Technical Engineer
>Office: (408) 970 - 7978
You have it backwards. There is PROFPEEK XEDIT, and all the other PROFxxx
x
XEDIT, are supposed to be on the S disk. They are for all users, and that
is where IBM puts them. They are not supposed to be on the A disk. You ca
n
do that, if you want to, but it is a bad idea, since when service comes
in, it goes on the S-disk and then the copy on your A disk is out-of-sync
.
The right way to do it is to create your own XEDIT profile as a front *
back end to the IBM one.
MYPRPEEK XEDIT A
Commands to customize.
'MACRO PROFPEEK'
Commands to customize.
Then issue DEFAULTS SET PEEK PROFILE MYPRPEEK once.
I have given examples in the past.
Is IBM breaking their own rules?
Alan Ackerman
Alan (dot) Ackerman (at) Bank of America (dot) com
