FDM is used to COPY a PDSE.LOAD (TYPE=LIBRARY) to a source PDSE LOAD. The target pdse is very large results in the B37; 6035 members. With FDM 7.8.1, the IEBCOPY temporary file that is used to house the IGW01551I and IGW01553I copy messages does not have the list of all members copied because the temporary file gets a B37.
Notification history appears to have duplicate recipient entries for repeat or escalated notifications. The notification date and time is shown with a list of recipients that is duplicated.
If you have a dp and p site to install to, after backing out and reverting the p site, the revert at dp gives message : Trace IN U=SERSTAR3,F1=MASTER,F2=WRITE,@TCA=10218000,Len=02019 MARK000000200003E800 VCA=10218000,USER=SERSTAR3, Duplicate Record F1=MASTER,F2=WRITE,KEY=MARK000000200003E800,RC=0008,FDBK=0008
If you run the CMPONENT HISTORY CREATE service twice for the same component/type/package, to create a duplicate component history record, the second (and subsequent) execution of the service correctly diagnoses a duplicate record, but the message text is: CMN8646A - Package Master record already exists The text should indicate Component Master.
If the TeamTrack Mail Client processes a message containing multi part/alternative content (both HTML and Plain Text), then the body of the e-mail will doubled in the TeamTrack field it is mapped to. We note this in the documentation of the include HTML feature of the Mail Client:
Please gather any applicable information from the list below and contact Dimensions Support for help with this error message . What you need to troubleshoot:
Simultaneous execution of build jobs for components in the same package may result in failures during execution of the staging job SUCCESS/CMNBATCH step. Typically the step will fail with a RC=12 and the following type of error message :
