Why do we get message COPYING TO UNKN when copying from PDSE to PDSE with CA PDSMAN FASTCOPY?
search cancel

Why do we get message COPYING TO UNKN when copying from PDSE to PDSE with CA PDSMAN FASTCOPY?

book

Article ID: 3994

calendar_today

Updated On:

Products

PDSMAN

Issue/Introduction

While testing PDSMAN r7.61 we get "UNKN" when copying from PDSE to PDSE. Had not seen this in prior release.

COPYING TO    UNKN   OUTDD=SYS00013 VOL=PRM#T3                                
DSN=HLQ.HOST.D080828.T133944.LTEM2.AH001                                   
        FROM POBJ   INDD=SYS00012 VOL=PRM#TT DSN=HLQ.APROD.SPLOAD2

Environment

PDSMAN 7.6

Cause

PDSMAN reports 'UNKN' when the output is a PDSE that has not been updated yet because at this point we don't know for sure whether it's a data or program library.

Resolution

In the past you may have seen "PDSE" instead of "UNKN". This was corrected by PDSMAN 7.6 Published Solution QO94439 which included several minor FASTCOPY corrections.


This PTF is also included in the base product for PDSMAN 7.6.1. One of the items in this APAR is:


  • The output data set type may be reported incorrectly as 'PDSE' instead of 'UNKN' on message FCO110I.