When ISPF fails to initialize just create a new dataset by entering the
following in the TMP READY PROMPT:
Alloc f(ISPPROF) da('your dsname') new catalog like(sys1.parmlib) /8 or any
other model dataset you can access with DCB/80/3120/fb
Itschak
On Tue, Jul 14, 2009 at 5:49 AM, Joel C Ewing <jcew...@acm.org> wrote:
> Having been there, these kinds of problems are more likely to hit you on a
> DR test, when you deliberately take only a subset of vaulted data to DR and
> don't have full access to ML2 data; especially when someone tries to fire up
> a personal TSO session that doesn't normally run during a DR test. The ISPF
> profile mostly contains just personal customization and old dialog panel
> field values, which can always be re-created if need be after scratching the
> unreachable ML2 ds. While not having your normal ISPF profile available is
> an annoyance, it's not a show stopper, even in a real DR - just delete and
> allow creation of a new profile.
>
> Obviously, any datasets that are essential to your z/OS recovery process,
> including essential TSO user datasets that will be needed before DFHSM is
> fully functional, need to have MGMTCLAS or other mechanisms to insure they
> are ineligible for migration (to ML1 or ML2). For DR testing, that
> restriction extends even to datasets needed after DFHSM is functional,
> unless the required media for recall will be taken for the test.
> JC Ewing
>
> Gibney, Dave wrote:
>
>> Urgent is non-descriptive.
>>
>> John's answer is how to continue, not how to access the dataset. You
>> can't access the existing dataset, you don't have it available at you DR
>> test. (I hope it's a test :)
>>
>> Dave Gibney
>> Information Technology Services
>> Washington State University
>>
>>
>> -----Original Message-----
>>> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
>>> Behalf Of John McKown
>>> Sent: Monday, July 13, 2009 6:17 PM
>>> To: IBM-MAIN@bama.ua.edu
>>> Subject: Re: Urgent
>>>
>>> On Tue, 14 Jul 2009, Jacky Bright wrote:
>>>
>>> My DBA has forgot to recall the SYSADM ISPF profile dataset from the
>>>>
>>> VTS.
>>>
>>>> Now at DR site entry is there in ML2 which we can not access.
>>>> Looking for a way how to access this dataset. Any ideas.
>>>> JAcky
>>>>
>>>> Do a DELETE ... NOSCRATCH
>>>
>>> However, for this to work with DFHSM down, you must connect the userid
>>> who
>>> is doing it to a special group - ARCCATGP
>>>
>>> http://publibz.boulder.ibm.com/cgi-
>>> bin/bookmgr_OS390/BOOKS/dgt2s671/4.8.12
>>>
>>> If necessary, you might need to create this group in RACF.
>>>
>>> As an alternative, you __might__ be able to use IDCAMS and do a
>>>
>>> REPRO MERGECAT -
>>> ENT(SYSADM.ispf.profile) -
>>> INDATASET(realucat) -
>>> OUTDATASET(someothercat)
>>>
>>> Of course, the absolute simpliest way is to delete the SYSADM alias
>>>
>> and
>>
>>> point it to another catalog. Of course, that implicitly uncatalogs all
>>> of
>>> SYSADM's datasets.
>>>
>>> --
>>>
>>> Maranatha!
>>> John McKown
>>>
>>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
