We (I) did the front/back end a bit differently. Since I want to supply a profile for ALL users, not only those who set a new default, I named my frontend "PROF...." (not only for peek), and renamed IBM's to "PIBM....". It works just like you say:
->PROFPEEK XEDIT A ->Commands to customize. ->'MACRO PIBMPEEK' ->Commands to customize. Then I rebuilt INSTSEG! Otherwise "INSTSEG on S" overrides my changes on the S-disk. And I put the PROF... and the PIBM.... in the segment. Shimon ---- Original message ---- >Date: Thu, 2 Apr 2009 18:07:48 -0500 >From: Alan Ackerman <alan.acker...@earthlink.net> >Subject: Re: Problem using the PEEK Command >To: IBMVM@LISTSERV.UARK.EDU > >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 PROFxxxx >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 can >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