Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace z/OS
Categories ICSF
Created by Guest
Created on Dec 16, 2025

ICSF - Preserve Joblog and write CSFO0230 details

Starting with zOS 3.2 ICSF is able to preserve the Joblog and make it available to JES even when started with SUB=MSTR. However, it does not yet support caching of the system settings and print them afterwards to the Joblog.

Currently, after JES availability the log shows:
[textbox formatting unfortunately not persisted when saving the 'code block']

********************************* TOP OF DATA **********************************************************************
J E S 2 J O B L O G -- S Y S T E M M 2 -- N O D E C H M 1 J E S 2

08.39.59 S0973413 ---- THURSDAY, 11 DEC 2025 ----
08.39.59 S0973413 CSFM042I ICSF RUNNING SUB=MSTR. JOB ENTRY SUBSYSTEM IS NOW ACTIVE. ICSF JOB LOG IS NOW AVAILABLE.
09.39.01 S0973413 IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00009

But it does not include the details it has written to Syslog and used for startup. However, this would be a real value add. When one can check that information again in the Joblog and not have to look for the Syslog from the IPL day (which can be weeks ago, offloaded somewhere).

The intention of this idea is to get the CSFO0230* messages cached (during IPL) and then written to the Joblog once JES is available to get something like:
[textbox formatting unfortunately not persisted when saving the 'code block']

********************************* TOP OF DATA **********************************************************************
J E S 2 J O B L O G -- S Y S T E M <sys> -- N O D E <node>

08.39.59 S0973413 ---- THURSDAY, 11 DEC 2025 ----
08.39.59 S0973413 CSFM042I ICSF RUNNING SUB=MSTR. JOB ENTRY SUBSYSTEM IS NOW ACTIVE. ICSF JOB LOG IS NOW AVAILABLE.
09.39.01 S0973413 IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00009
09.39.01 S0973413 IEE252I MEMBER CSFPRM00 FOUND IN SYS1.PARMLIB

09.39.01 S0973413 IEF196I CSFM708I THE INSTALLATION OPTIONS HAVE BEEN READ FROM MEMBER
09.39.01 S0973413 IEF196I CSFPRM00 IN DDNAME CSFPARM2.
09.39.01 S0973413 IEF196I CSFO0230 CKDSN(<ckdsn>)
09.39.01 S0973413 IEF196I CSFO0230 PKDSN(<ckdsn>)
09.39.01 S0973413 IEF196I CSFO0230 TKDSN(<ckdsn>)
09.39.01 S0973413 IEF196I CSFO0230 COMPAT(<yes|no>)
09.39.01 S0973413 IEF196I CSFO0230 DOMAIN(<domain>)
09.39.01 S0973413 IEF196I CSFO0230 SSM(<yes|no>)
09.39.01 S0973413 IEF196I CSFO0230 STATS(ENG,SRV,ALG)
09.39.01 S0973413 IEF196I CSFO0230 CHECKAUTH(<yes|no>)
09.39.01 S0973413 IEF196I CSFO0230 USERPARM(<parm>)
09.39.01 S0973413 IEF196I CSFO0230 REASONCODES(ICSF)
09.39.01 S0973413 IEF196I CSFO0230 SYSPLEXCKDS(YES,FAIL(YES))
09.39.01 S0973413 IEF196I CSFO0230 SYSPLEXPKDS(YES,FAIL(YES))
09.39.01 S0973413 IEF196I CSFO0230 SYSPLEXTKDS(YES,FAIL(YES))
09.39.01 S0973413 IEF196I CSFO0230 DEFAULTWRAP(ENHANCED,ENHANCED)
09.39.01 S0973413 IEF196I CSFO0230 AUDITKEYLIFECKDS(TOKEN(YES),LABEL(YES))
09.39.01 S0973413 IEF196I CSFO0230 AUDITKEYLIFEPKDS(TOKEN(YES),LABEL(YES))
09.39.01 S0973413 IEF196I CSFO0230 AUDITKEYLIFETKDS(TOKENOBJ(YES),SESSIONOBJ(YES))
09.39.01 S0973413 IEF196I CSFO0230 AUDITKEYUSGCKDS(TOKEN(YES),LABEL(YES),INTERVAL(4))
09.39.01 S0973413 IEF196I CSFO0230 AUDITKEYUSGPKDS(TOKEN(YES),LABEL(YES),INTERVAL(4))
09.39.01 S0973413 IEF196I CSFO0230 AUDITPKCS11USG(TOKENOBJ(YES),SESSIONOBJ(YES),
09.39.01 S0973413 IEF196I NOKEY(YES),INTERVAL(4))
09.39.01 S0973413 IEF196I CSFO0230 TRACKCLASSUSAGE(DATADEC,DATAENC)
09.39.01 S0973413 IEF196I CSFO0230 KDSREFDAYS(1)

CSFO0230:
This message is issued once for each option in the ICSF Options Data Set. This message is informational only. No action is required.

Idea priority High
  • Guest
    Dec 16, 2025
    Thank you for the requirement. This will be added to our backlog for consideration as a future release candidate. I sent the customer an email suggesting the "DISPLAY ICSF" operator command as work around in the meantime, to write ICSF environment information to the joblog.