There is a SMPE program, GIMXSID that can be used to provide a CSI 
report.  I found the JCL on one of the Shop/z help screens, it is something 
similar to the following:

        //STEP1    EXEC PGM=GIMXSID,PARM='WAIT=10MIN,L=ENU'                
        //SYSPRINT DD SYSOUT=*                                             
        //SMPOUT   DD SYSOUT=*                                             
        //SMPXTOUT DD DSN=your.output.dat.set,DISP=(NEW,CATLG),         <<< 
Update           
        //            DCB=(RECFM=FB,LRECL=12560,BLKSIZE=25120),            
        //            SPACE=(TRK,(10,10)),VOL=SER=xxxxxx,UNIT=SYSALLDA         
        //*SMPXTOUT DD PATH='/EXISTING_DIRECTORY/NEW_FILE',                     
<<< Update for zfs file report 
        //*            PATHOPTS=(OWRONLY,OCREAT,OTRUNC),                   
        //*            FILEDATA=BINARY,PATHMODE=(SIRWXU,SIRWXG,SIRWXO)     
        //SYSIN    DD DATA,DLM=$$                                          
        CSI=your.smpe.csi.dataset                                               
<<< Update                                      
        TARGET=targetzonename                                           <<< 
Update                                                     
        $$  

        The creates the CSI report that you would upload to Shop/z when 
ordering with a report!!! It is a muchn abbreviated listing of the FMID and 
features in you SMPE CSI.     
        I run this and then rummage through the report to add/delete FMID from 
my ASAP profile.

        Hth
        Tony

                                                         

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Tuesday, June 05, 2018 5:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: ASAP profile setup

I’ve used IBM ServiceLink ASAP for years to get early heads-up on support 
concerns. My goal is to monitor most components in our z/OS environment. The 
only way I know to set up a profile is to add each ‘significant’ FMID. Some 
issues:

-- I've settled on 'significant' as those installed FMIDs that are not 
obviously dependents of some other FMID. For example, the FMID for COBOL 4.2 is 
HADB420. COBOL Japanese support is JADB422. SMPE indicates this relationship 
when listing JADB422 with 'FMID:    HADB420'. For ASAP, JADB422 does not need 
to be monitored separately from HADB420, so there's no point in adding it to my 
profile. 

-- New FMIDs need to be added to my profile.

-- Some FMIDs change or disappear from release to release. At some point it 
pays to delete FMIDs that no longer run in the shop.

Is there a simple(r) way to manage a profile than listing out SMPE sysmods and 
rummaging through the pile for gems? My profile currently has around 100 FMIDs 
for z/OS 2.1. I need to update it for 2.3, keeping 2.1 for the time being. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com



----------------------------------------------------------------------
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

Reply via email to