Your experience matches mine, though MISSINGFIX may indicate PTFs to order/receive.
FIXCAT appeared in SMP/E V3R5.0 for z/OS V1R10.0 Commands (SA22-7771-12), Thirteenth Edition, September 2008. APPLY SOURCEID syntax only seems to hint about FIXCAT with two examples and mention of mixed case source IDs--sees Notes 1 and 8 below. Note 1: The following examples are valid source IDs: RSU0709 RSU* IBM.Device.20%4 IBM.Device.*.zAAP Note 8: A source ID value might contain mixed case alphabetic characters. However, SMP/E ignores the case when identifying matches for a specified source ID value. For example, a specified source ID value of ABCDEF matches a value of abcdef. A couple of sentences from https://www.ibm.com/support/pages/node/665129 may offer enough insight: During SMP/E RECEIVE command processing, SMP/E translates fix category values into source IDs and assigns them to the resolving (fixing) PTFs identified on the HOLDDATA. You can then use the fix category values as source IDs when selecting a set of PTFs to be applied. Regards, Kevin -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of MARTIN, MIKE Sent: Friday, February 7, 2020 11:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMPE APPLY SOURCEID vs FIXCAT Hi all, I am trying to figure out the difference between using SOURCEID vs. FIXCAT for an APPLY? Example below... APPLY CHECK SOURCEID (IBM.Function.GlobalMirror) APPLY CHECK FIXCAT (IBM.Function.GlobalMirror) And one more curiosity... If I run a the APPLY statements that get PUNCH'd from the following REPORT FIXCAT, is it the same as doing the APPLY FIXCAT above? REPORT MISSINGFIX ZONES (TGTRES) FIXCAT (IBM.Function.GlobalMirror) Any insights are greatly appreciated. Mike Martin This email may contain confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please contact the sender and delete all copies. Any review or distribution by others is strictly prohibited. Personal emails are restricted by policy of the State Employees' Credit Union (SECU). Therefore SECU specifically disclaims any responsibility or liability for any personal information or opinions of the author expressed in this email. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
