It will be important to understand clearly about your current SAS code-script processing that is used to perform any cost-accounting data-table associations that map your IDMS environment (system, CVs, USERIDs, transactions, program-names, other attributes) to a suitable cost-accounting identification string(s). One would expect that you will need to coordinate time/effort with the MXG software admin, which handles the MXG IDMS/PERFMON SMF data decoding -- that challenge will need to be addressed with some other programming solution / reporting utility, in order to extract the key/required data-fields from each IDMS SMF PMAM transaction record for harvesting both "identification data-values" and also event timestamps and your site's choice for "consumption" metrics, such as CPU-time.
Likely this process is processed today, either daily or monthly, depending on your downstream accounting-software data-feed requirements but also IDMS PERFMON SMF data-volume.
Frankly, if your site is seriously considering just such a "replacement" for cost-accounting / chargeback for IDMS, I'd expect you will be experiencing similar challenges with all of your z/OS MVS cost-areas (e.g., 1) batch, TSO, started-tasks using SMF 30 data, 2) CICS using SMF 110 subtype 1 data, 3) DB2 using SMF 101 thread/package data, and so on). Each of these "topic areas" have their own distinct challenges when addressing IT Resource Mgmt Cost-Allocation / Chargeback / Show-Back / <whatever>.
Wish you luck with your challenge at-hand, Johan !!
Regards,
Scott Barry
SBBTech LLC