,I qiut
the PDS pressing
F3.The PDS isn't released immediately.
Could you tell me what' s wrong with me? How to release PDS by Partial
Release = YI
Thanks a lot!
Best Regads,
Jason Cai
--
For IBM-MAIN
what was the allocation of space while allocating the PDS and once you came
out of the PDS using F3?
YI indicate it should be released with space management cycle run and also
when close is issued against the dataset..
I assume by mistake or by other job/user dataset was not opened...sometime
(IBMUSER.PDS) which space is cyl(200,200,50).
>
> I insert many members into th PDS by p.3.4 and update the member .Then ,I
> qiut the PDS pressing
>
> F3.The PDS isn't released immediately.
>
> Could you tell me what' s
On Mon, 9 May 2011 08:10:57 -0700, Ron Hawkins wrote:
>
>I suspect that when you add a member to a PDS using ISPF that you are not
>satisfying all of the conditions described in "USING DATASETS 3.2.5.4
>Releasing Space." I leave to other to define which one it may be, or
>disagree.
>
>My guess is t
ot!
Best Regards,
Jason Cai
发件人: Ron Hawkins
发送时间: 2011-05-09 23:11:00
收件人: IBM-MAIN
抄送:
主题: Re: How to release PDS by Partial Release = YI
Jason,
I suspect that when you add a member to a PDS using ISPF that you are not
satisfying all of the conditions described in "USING DATASE
--Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of ibmnew
> Sent: Tuesday, May 10, 2011 3:53 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: How to release PDS by Partial Release = YI
>
> Dear
>
> Yes. You are right.
uesday, May 10, 2011 3:53 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: [IBM-MAIN] How to release PDS by Partial Release = YI
>
> Dear
>
> Yes. You are right. Thanks a lot!
>
> I started DFHSM up in our shop today.
>
> I want to Release unused and overallocated
> 1. How many times can PSM be run in one
> day?
Running Automatic Primary Space Management Multiple Times a Day
Issue one or both of the following PATCH commands:
PATCH .MCVT.+414 X''
> 2.Why wasn't IBMUSER.PDS2 released?
The following msg is in the log of HSM
The reason code say:
*41*The volume where the migration copy has been allocated (as returned by
DYALLOC) is not the same volume that DFSMShsm has requested. In an SMS
environment, the data set is allocated to SMS-managed storage.
*40,* *41*Update the SMS storage class routine so migration copies a
9 matches
Mail list logo