Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Delivered
Created by Guest
Created on Jan 18, 2017

Filemgr not working with DFSMS SYS% facility

We are currently running z/OS 2.2 with FM Release 13.01.

We use the DFSMS SYS% facility in order to clone our systems.
SYS% allows you to reference the same data set one a different volume.
You can read more about it in the DFSMS Managing Catalogs manual.

For example:

SYS1.PARMLIB is our running / executing environment
This dataset resides on the ‘A' side volume BIBMA1 –where A indicate the A running side

SYSO.PARMLIB is our back up / Old environment
This dataset resides on the ‘B' side volume BIBMB1 –where B indicates the B old side

Using this method, we clone our entire operating system and all of it components making it very easy to implement and back out.
Anyway, occasionally after we build an environment it is necessary to change a member on the non-running side.

All IBM utilities respect this SYS% and you can access a non- running dataset by specifying SYSO (oh) in your JCL:

DSN=SYSO.PARMLIB,DISP=(SHR)….

When we migrated from STARTOOL to FILEMGR we had to change our JCL accordingly.
Part of our build process needs to change a member on the old side.
What happened with FM is it didn't respect the SYS% and actually changed the running environment – which is very dangerous in our case.

I set up the following test to show you the results:

I set up two datasets – this is on the Running side (A side)
Data Set Name . . . : SYS1.MM.TEST
General Data
Volume serial . . . : BOEMA1 <- A side

Data Set Name . . . : SYS1.MM.TEST
General Data
Volume serial . . . : BOEMB1 <- B side

Physically both datasets are SYS1.MM.TEST, however you can reference the second one by specifying
SYSO.MM.TEST (that's SYS oh)

I used this JCL to attempt to update the SYSO side and it updated the running dataset.
Here is the JCL I used:

//FILEMGR EXEC PGM=FMNMAIN
//SYSPRINT DD SYSOUT=*
//SYSMDUMP DD SYSOUT=*
//IDIOFF DD DUMMY
//FMNTSPRT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
//SYSIN DD *
$$FILEM SET HEADERPG=NO,PAGESIZE=60,DATAHDR=NO
$$FILEM SET WIDEPRT=YES,PRTTRANS=ON
$$FILEM FCH ,
$$FILEM MEMBER=TESTNEW,
$$FILEM PACK=ASIS,
$$FILEM DSNIN=SYSO.MM.TEST  SYSO
C C'TEST' C'PROD'
//*

Idea priority Medium
  • Guest
    Reply
    |
    Mar 25, 2021

    This has been delivered in PTF UI74115

  • Guest
    Reply
    |
    Mar 24, 2021

    Hello,

    Thank you for taking the time to provide your ideas to IBM. This request has been delivered in our most recent Continuous Delivery Update 14.1.13.

    Our team truly values our relationship with you, and we appreciate your willingness to share your recommendations and ideas.

    If you have any additional feedback or thoughts, or if there is anything else we can do, please do not hesitate to reply to this message to continue the conversation.

    Thanks so much,

    The IBM File Manager for z/OS team

  • Guest
    Reply
    |
    Nov 13, 2019

    You mentioned you need more information, but I have clearly provided the JCL used to recreate this situation. You would need to turn SYS% on in your lab in order to test. Please read DFSMS Managing Catalogs - SYS% facility for more information.

    While I do have a circumvention, as a company IBM manages and maintains DFSMS and since FILEMGR is an IBM product and deals with datasets, they should also support the features of DFSMS.

    Let me know if you need additional information.

  • Guest
    Reply
    |
    Nov 12, 2019

    The example provided specifies the data set name as the parameter for FCH. Have you tried using a DD card as you appear to have done for STARTOOL. So instead of coding DSNIN= as the keyword use INPUT=ddname or remove the keyword and simply code a //DDIN DD ...... that FCH will pick up. Could provide feedback whilst we investigate our allocation process for the DSNIN.