search cancel

Endevor Package Ship DSN Mapping Rules

book

Article ID: 134073

calendar_today

Updated On:

Products

Endevor Software Change Manager (SCM) Endevor Software Change Manager - Natural Integration (SCM) Endevor Software Change Manager - ECLIPSE Plugin (SCM) Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

An SE37-04 abend on package ship was received. A check was done  on the DSN Mapping Rule for the dataset and it does not appear to be working. 

The value in the field "Approx Host Members/Cyl" looks like it is picking up the default of 16 members per CYL.

 

Cause

If a dataset not excluded and is not found to match any DSN MAPPING dataset, then the default will be used.

The default will have Approx Host Members/Cyl=16 and the dataset will map to it's self. So mapping to the remote LPAR with the same DSN as the host.

Environment

Release :

Component : CA Endevor Software Change Manager

Resolution

This is how DSN Mapping Rule selection works. 

1)The dataset is compared to the excludes.  If it find a match the dataset is excluded from selection.

2)The dataset is compared  DSN Mapping Rules if it find a match that DSM Mapping rule is used.

3)The default will be used. This being Approx Host Members/Cyl=16 and the dataset will map to it's self.


It is recommended that you use option T - Test DSN Mapping Rules . This will give you a indication what  or if a rule is being selected.



Additional Information

Examples:

1)

HOST DATASET NAME ===> *.*

If the dataset is BST.PROD.LOADLIB then the above mapping will not be selected.

2)

HOST DATASET NAME ===> *.* .*

If the dataset is BST.PROD.LOADLIB then the above mapping will be selected.


3)

HOST DATASET NAME ===> *.* .LOADLIB

If the dataset is BST.PROD.LOADLIB then the above mapping will be selected.