Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

The members you listed all start with the SET name and have a suffix that describes their purpose.  I see you have had 2 sets, YSYS5 and YSYS5T.  No, those suffixes are not documented.

The null suffix identifies the CARLa code running in C2POLICE for the alert set.

These members are generated by the Verify action (that's the V in the position right after the SET name) and the Refresh action (the others).  Those members must not be exported, but instead generated in the target C2PCUST using the Verify and Refresh line commands, or the comparable batch job.

There are potentially also SENSxxxx and PCIxxxx members in C2PCUST, set through SE.A.S and SE.A.P.

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Rob,

This isn't a C2PCUST I created, rather one I have inherited. And, according to the SE.A.A panel, there is no YSYS5T configuration, although there is YSYS5C configuration. I fear this library is corrupt in some way, and I maybe better off re-building from scratch.
Your reply that the YSYS5 members should NOT be transported was a BIG surprise. So just where is the YSYS5 config held? I assume it must be in the C2PIUACF and C2PIUEMF members.

That list of members and their use would be so helpful.
Lennie

The members you listed all start with the SET name and have a suffix that describes their purpose.  I see you have had 2 sets, YSYS5 and YSYS5T.  No, those suffixes are not documented.

The null suffix identifies the CARLa code running in C2POLICE for the alert set.

These members are generated by the Verify action (that's the V in the position right after the SET name) and the Refresh action (the others).  Those members must not be exported, but instead generated in the target C2PCUST using the Verify and Refresh line commands, or the comparable batch job.

There are potentially also SENSxxxx and PCIxxxx members in C2PCUST, set through SE.A.S and SE.A.P.

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Rob,

This isn't a C2PCUST I created, rather one I have inherited. And, according to the SE.A.A panel, there is no YSYS5T configuration, although there is YSYS5C configuration. I fear this library is corrupt in some way, and I maybe better off re-building from scratch.
Your reply that the YSYS5 members should NOT be transported was a BIG surprise. So just where is the YSYS5 config held? I assume it must be in the C2PIUACF and C2PIUEMF members.

That list of members and their use would be so helpful.
Lennie

The members you listed all start with the SET name and have a suffix that describes their purpose.  I see you have had 2 sets, YSYS5 and YSYS5T.  No, those suffixes are not documented.

The null suffix identifies the CARLa code running in C2POLICE for the alert set.

These members are generated by the Verify action (that's the V in the position right after the SET name) and the Refresh action (the others).  Those members must not be exported, but instead generated in the target C2PCUST using the Verify and Refresh line commands, or the comparable batch job.

There are potentially also SENSxxxx and PCIxxxx members in C2PCUST, set through SE.A.S and SE.A.P.

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

> Once you DELETE a set from SE.A.A, the set is deleted from the internal tables, but the work files are not.
I think that was changed last year. You now have the option (slash on a popup) to delete all the members for the configuration.

Rob,

This isn't a C2PCUST I created, rather one I have inherited. And, according to the SE.A.A panel, there is no YSYS5T configuration, although there is YSYS5C configuration. I fear this library is corrupt in some way, and I maybe better off re-building from scratch.
Your reply that the YSYS5 members should NOT be transported was a BIG surprise. So just where is the YSYS5 config held? I assume it must be in the C2PIUACF and C2PIUEMF members.

That list of members and their use would be so helpful.
Lennie

The members you listed all start with the SET name and have a suffix that describes their purpose.  I see you have had 2 sets, YSYS5 and YSYS5T.  No, those suffixes are not documented.

The null suffix identifies the CARLa code running in C2POLICE for the alert set.

These members are generated by the Verify action (that's the V in the position right after the SET name) and the Refresh action (the others).  Those members must not be exported, but instead generated in the target C2PCUST using the Verify and Refresh line commands, or the comparable batch job.

There are potentially also SENSxxxx and PCIxxxx members in C2PCUST, set through SE.A.S and SE.A.P.

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Rob and Guus,

Thanks for that information. Explains more.

I am not seeing a slash option on a popup when I attempt a DELETE, but maybe that is a zSecure maintenance level issue.

Rob,

We have decided that the custom alerts that have been defined are no longer required. However, we would like to keep all the definitions in case we change our minds later on. So is there a method of excluding them from the EXPORT or IMPORT functions?
Regards, Lennie

> Once you DELETE a set from SE.A.A, the set is deleted from the internal tables, but the work files are not.
I think that was changed last year. You now have the option (slash on a popup) to delete all the members for the configuration.

Rob,

This isn't a C2PCUST I created, rather one I have inherited. And, according to the SE.A.A panel, there is no YSYS5T configuration, although there is YSYS5C configuration. I fear this library is corrupt in some way, and I maybe better off re-building from scratch.
Your reply that the YSYS5 members should NOT be transported was a BIG surprise. So just where is the YSYS5 config held? I assume it must be in the C2PIUACF and C2PIUEMF members.

That list of members and their use would be so helpful.
Lennie

The members you listed all start with the SET name and have a suffix that describes their purpose.  I see you have had 2 sets, YSYS5 and YSYS5T.  No, those suffixes are not documented.

The null suffix identifies the CARLa code running in C2POLICE for the alert set.

These members are generated by the Verify action (that's the V in the position right after the SET name) and the Refresh action (the others).  Those members must not be exported, but instead generated in the target C2PCUST using the Verify and Refresh line commands, or the comparable batch job.

There are potentially also SENSxxxx and PCIxxxx members in C2PCUST, set through SE.A.S and SE.A.P.

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Rob and Guus,

Thanks for that information. Explains more.

I am not seeing a slash option on a popup when I attempt a DELETE, but maybe that is a zSecure maintenance level issue.

Rob,

We have decided that the custom alerts that have been defined are no longer required. However, we would like to keep all the definitions in case we change our minds later on. So is there a method of excluding them from the EXPORT or IMPORT functions?
Regards, Lennie

> Once you DELETE a set from SE.A.A, the set is deleted from the internal tables, but the work files are not.
I think that was changed last year. You now have the option (slash on a popup) to delete all the members for the configuration.

Rob,

This isn't a C2PCUST I created, rather one I have inherited. And, according to the SE.A.A panel, there is no YSYS5T configuration, although there is YSYS5C configuration. I fear this library is corrupt in some way, and I maybe better off re-building from scratch.
Your reply that the YSYS5 members should NOT be transported was a BIG surprise. So just where is the YSYS5 config held? I assume it must be in the C2PIUACF and C2PIUEMF members.

That list of members and their use would be so helpful.
Lennie

The members you listed all start with the SET name and have a suffix that describes their purpose.  I see you have had 2 sets, YSYS5 and YSYS5T.  No, those suffixes are not documented.

The null suffix identifies the CARLa code running in C2POLICE for the alert set.

These members are generated by the Verify action (that's the V in the position right after the SET name) and the Refresh action (the others).  Those members must not be exported, but instead generated in the target C2PCUST using the Verify and Refresh line commands, or the comparable batch job.

There are potentially also SENSxxxx and PCIxxxx members in C2PCUST, set through SE.A.S and SE.A.P.

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Rob,

Thanks. Works fine.
Lennie

Rob and Guus,

Thanks for that information. Explains more.

I am not seeing a slash option on a popup when I attempt a DELETE, but maybe that is a zSecure maintenance level issue.

Rob,

We have decided that the custom alerts that have been defined are no longer required. However, we would like to keep all the definitions in case we change our minds later on. So is there a method of excluding them from the EXPORT or IMPORT functions?
Regards, Lennie

> Once you DELETE a set from SE.A.A, the set is deleted from the internal tables, but the work files are not.
I think that was changed last year. You now have the option (slash on a popup) to delete all the members for the configuration.

Rob,

This isn't a C2PCUST I created, rather one I have inherited. And, according to the SE.A.A panel, there is no YSYS5T configuration, although there is YSYS5C configuration. I fear this library is corrupt in some way, and I maybe better off re-building from scratch.
Your reply that the YSYS5 members should NOT be transported was a BIG surprise. So just where is the YSYS5 config held? I assume it must be in the C2PIUACF and C2PIUEMF members.

That list of members and their use would be so helpful.
Lennie

The members you listed all start with the SET name and have a suffix that describes their purpose.  I see you have had 2 sets, YSYS5 and YSYS5T.  No, those suffixes are not documented.

The null suffix identifies the CARLa code running in C2POLICE for the alert set.

These members are generated by the Verify action (that's the V in the position right after the SET name) and the Refresh action (the others).  Those members must not be exported, but instead generated in the target C2PCUST using the Verify and Refresh line commands, or the comparable batch job.

There are potentially also SENSxxxx and PCIxxxx members in C2PCUST, set through SE.A.S and SE.A.P.

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Rob,

I nevertheless have a problem now. The configuration I exported and then imported was SET(YSYS5) ALERT(1*). However, I then end up without the YSYS5P member in the target C2PCUST data set. This member is needed for the started task. Should I also copy this member? You stated above that my YSYS5 members MUST NOT be exported. 
Please explain what I need to do?

Thanks

Lennie

Rob,

Thanks. Works fine.
Lennie

Rob and Guus,

Thanks for that information. Explains more.

I am not seeing a slash option on a popup when I attempt a DELETE, but maybe that is a zSecure maintenance level issue.

Rob,

We have decided that the custom alerts that have been defined are no longer required. However, we would like to keep all the definitions in case we change our minds later on. So is there a method of excluding them from the EXPORT or IMPORT functions?
Regards, Lennie

> Once you DELETE a set from SE.A.A, the set is deleted from the internal tables, but the work files are not.
I think that was changed last year. You now have the option (slash on a popup) to delete all the members for the configuration.

Rob,

This isn't a C2PCUST I created, rather one I have inherited. And, according to the SE.A.A panel, there is no YSYS5T configuration, although there is YSYS5C configuration. I fear this library is corrupt in some way, and I maybe better off re-building from scratch.
Your reply that the YSYS5 members should NOT be transported was a BIG surprise. So just where is the YSYS5 config held? I assume it must be in the C2PIUACF and C2PIUEMF members.

That list of members and their use would be so helpful.
Lennie

The members you listed all start with the SET name and have a suffix that describes their purpose.  I see you have had 2 sets, YSYS5 and YSYS5T.  No, those suffixes are not documented.

The null suffix identifies the CARLa code running in C2POLICE for the alert set.

These members are generated by the Verify action (that's the V in the position right after the SET name) and the Refresh action (the others).  Those members must not be exported, but instead generated in the target C2PCUST using the Verify and Refresh line commands, or the comparable batch job.

There are potentially also SENSxxxx and PCIxxxx members in C2PCUST, set through SE.A.S and SE.A.P.

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie

Rob,

I nevertheless have a problem now. The configuration I exported and then imported was SET(YSYS5) ALERT(1*). However, I then end up without the YSYS5P member in the target C2PCUST data set. This member is needed for the started task. Should I also copy this member? You stated above that my YSYS5 members MUST NOT be exported. 
Please explain what I need to do?

Thanks

Lennie

Rob,

Thanks. Works fine.
Lennie

Rob and Guus,

Thanks for that information. Explains more.

I am not seeing a slash option on a popup when I attempt a DELETE, but maybe that is a zSecure maintenance level issue.

Rob,

We have decided that the custom alerts that have been defined are no longer required. However, we would like to keep all the definitions in case we change our minds later on. So is there a method of excluding them from the EXPORT or IMPORT functions?
Regards, Lennie

> Once you DELETE a set from SE.A.A, the set is deleted from the internal tables, but the work files are not.
I think that was changed last year. You now have the option (slash on a popup) to delete all the members for the configuration.

Rob,

This isn't a C2PCUST I created, rather one I have inherited. And, according to the SE.A.A panel, there is no YSYS5T configuration, although there is YSYS5C configuration. I fear this library is corrupt in some way, and I maybe better off re-building from scratch.
Your reply that the YSYS5 members should NOT be transported was a BIG surprise. So just where is the YSYS5 config held? I assume it must be in the C2PIUACF and C2PIUEMF members.

That list of members and their use would be so helpful.
Lennie

The members you listed all start with the SET name and have a suffix that describes their purpose.  I see you have had 2 sets, YSYS5 and YSYS5T.  No, those suffixes are not documented.

The null suffix identifies the CARLa code running in C2POLICE for the alert set.

These members are generated by the Verify action (that's the V in the position right after the SET name) and the Refresh action (the others).  Those members must not be exported, but instead generated in the target C2PCUST using the Verify and Refresh line commands, or the comparable batch job.

There are potentially also SENSxxxx and PCIxxxx members in C2PCUST, set through SE.A.S and SE.A.P.

Rob,
Thanks for help as always.
The C2PCUST library contains 191 members, most of which are associated with configurations I don't want. The current configuration is names YSYS5 and this is the one I wanted exported and imported. In the original library there are many members (191 in total), including the following, which start with YSYS5. I expected some of these to be transported.

It would really help to have a definitive list of the potential members of C2PCUST with details of their use, and when they are created and so on. Have I missed that in the documentation?

Lennie

YSYS5   
YSYS5A   
YSYS5E   
YSYS5P   
YSYS5S   
YSYS5TA   
YSYS5TE   
YSYS5TP   
YSYS5TS   
YSYS5TV   
YSYS5TVA   
YSYS5TVE   
YSYS5TVO   
YSYS5TVP   
YSYS5TVS   
YSYS5TV1   
YSYS5T1   
YSYS5V   
YSYS5VA   
YSYS5VE   
YSYS5VO   
YSYS5VP
YSYS5VS
YSYS5V1
YSYS51

Hi Rob, I assume you're right. Thanks and regards, Paul. 

Hi Paul

The IMPORT code in C2PESETP checks for every member in the transport file if the P_MEMBER value is empty, i.e., no MEMBER( ) parameter was specified, or P_MEMBER matches the member name in the transport file.  So, no, I do not think you have to specify the member names on IMPORT, unless you want to suppress some members.  You DO have to code REP(... MEMBER) or REP(*) if you intend to replace existing members in the target C2PCUST.

If your testing shows that MEMBER(name) must be coded on IMPORT, you've found a "not working as designed" condition, because the previous paragraph is from my design, 5 years ago.  You have a point though, the documentation states that * is the default value for SET( ), ALERT( ), but this is not documented for MEMBER( ).

Hi Lennie,

I think you should also specify the member selection on the import. 

Thanks and regards,

Paul. 

Greetings,

I am trying to change from using separate C2PCUST data sets per LPAR, to using a single C2PCUST for a sysplex. I have been trying to use C2PCUTIL to export and import the necessary definitions from the old C2PCUST datasets to a new one. I am confused about what options i need to set on the EXPORT and IMPORT statements. I have used the following EXPORT,

       ISPSTART CMD(%C2PESETP EXPORT SET(YSYS5) MEMBER(*) DD(TRANSPRT))

and this for IMPORT,
       ISPSTART CMD(%C2PESETP IMPORT SET(*) ADD(*) DD(TRANSPRT)) 

But I seem to be missing many members of the YSYS5 configuration.
The documentation seems to assume I know which members I need, but this is far from true!
Lennie