zfolder dataset definition not work for ISPF client?

Hi
The zFolder containing the zFiles should have a Data Set Definition (DSD) associated to it. In the DSD you are able to define the physical characteristics of the PDSE that we will create (if it does not already exist) when loading the files onto zOS.

Guy

Hi
The zFolder containing the zFiles should have a Data Set Definition (DSD) associated to it. In the DSD you are able to define the physical characteristics of the PDSE that we will create (if it does not already exist) when loading the files onto zOS.

Guy

I do define a Dataset definition for the Zfolder, which is (5,30)
sometime ,the definition work
sometime ,it does not work

Hi

If the PDS does not exist then we will create it using the physical characteristics specified in the DSD. If the PDS already exists then we do not check to verify that size specified in the DSD is the same as existing PDS. This could be what you are seeing.... the PDS was created by someone or something other than the build process with the smaller size. In this case we are not going to delete the PDS and recreate it.

If you are absolutely certain that the PDS did not exists before the build and it is the build process creating the PDS with the incorrect size characteristics then you should go through the IBM support process and get an APAR opened for this.

Guy

Hi

If the PDS does not exist then we will create it using the physical characteristics specified in the DSD. If the PDS already exists then we do not check to verify that size specified in the DSD is the same as existing PDS. This could be what you are seeing.... the PDS was created by someone or something other than the build process with the smaller size. In this case we are not going to delete the PDS and recreate it.

If you are absolutely certain that the PDS did not exists before the build and it is the build process creating the PDS with the incorrect size characteristics then you should go through the IBM support process and get an APAR opened for this.

Guy

I create PDS not through build process,
I use RTC ISPF client to load zcomponent from rtc server to Z/OS and edit the source file.
I found if the PDS is exist,the rtc will recreate it.

Through some tests,I found the problem is not related with Z/os user id ,but it is related with alias which is very odd.
The developer use his Z/os use id,throught RTC ISPF ,load a component which has a zfolder with thousands of zfile to z/os on his own alias, load failed,but when he load to a public alias, load succeed.
I use my z/os useid load the some component to z/os on my own alias, load succeed,but when I load the component on developer alias,load failed.I have the authority to edit developer alias.
I discuss the problem with our system administrator ,they said there are not restrict with alias.

Hi

I just tried this using the ISPF client and a load through the ISPF client does not delete an existing PDS. If it is there then we use it whether the size characteristics match the DSD or not. This makes complete sense as if the PDS contains members then it would be very wrong of us to delete the PDS since we have no idea where these existing members come from.

If you try this again and still think that the ISPF client load is deleting a pre-existing PDS then you need to open a PMR up with the IBM support center so we can look more closely at your set up.

Guy

Hi

I am not sure what you mean by 'alias'. Do you mean the High Level Qualifier (HLQ) that you specify when you load a component?

The ISPF client, when asking for the PDS creation will always use the size parameters specified in the DSD. Perhaps (if alias == hlq) you have some system rules set up that will override what the ISPF client is asking for. Perhaps you could test this theory by writing some JCL that allocates a PDS using the HLQ that is causing you problems. The JCL would specify the same size parameters that are set in the DSD. See what happens..... if the PDS is created but with the wrong size parameters then you know it is some system setup you have and nothing to do with the ISPF client.

Guy

Hi

I am not sure what you mean by 'alias'. Do you mean the High Level Qualifier (HLQ) that you specify when you load a component?

The ISPF client, when asking for the PDS creation will always use the size parameters specified in the DSD. Perhaps (if alias == hlq) you have some system rules set up that will override what the ISPF client is asking for. Perhaps you could test this theory by writing some JCL that allocates a PDS using the HLQ that is causing you problems. The JCL would specify the same size parameters that are set in the DSD. See what happens..... if the PDS is created but with the wrong size parameters then you know it is some system setup you have and nothing to do with the ISPF client.

Guy

HI Guy
You are right,the alias=HLQ
developer define new PDS thrtough P.3.2 ,and use parameter (5,30),and copy all source file into the new PDS, there are no problem , the definition and copy both success,which means maybe there are no system limited for the alias.
then the developer use the PDS which just create to load source through RTC ISPF,then found load failed only part of source load into z/os and the parameter of the PDS changed into (1,30).

Hi

ok, I think it is time for you to open up a PMR through IBM support. We would want to get more details from you and this forum would not be the right place to do this.

Guy