Why does the message COPYING TO UNKN occur when copying from PDSE to PDSE with PDSMAN FASTCOPY?
search cancel

Why does the message COPYING TO UNKN occur when copying from PDSE to PDSE with PDSMAN FASTCOPY?

book

Article ID: 3994

calendar_today

Updated On:

Products

PDSMAN

Issue/Introduction

While testing PDSMAN r7.6.1 FASTCOPY, the message "COPYING TO UNKN" occurs when copying from PDSE to PDSE.

COPYING TO    UNKN   OUTDD=SYS00013 VOL=volser                                
DSN=HLQ.HOST.D080828.T133944.LTEM2.AH001                                   
        FROM POBJ   INDD=SYS00012 VOL=volser 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 it is not known whether it's a data or program library.

Resolution

In the past, the message "PDSE" instead of "UNKN" occurred. 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.