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 Submitted
Created by Guest
Created on Dec 13, 2024

Add possibility to specify SYMBOLS=EXECSYS on a dd_input (zos_mvs_raw)

In a JCL job I can work with system symblols in in-stream datasets if I specify SYMBOLS=EXECSYS. I could not find a solution to do so with zos_mvs_raw.

JCL Example with &YYMMDD-Symbol (current date):

//COPYDS1 EXEC PGM=ADRDSSU,REGION=64M                     
//*****************************************************   
//SYSPRINT DD SYSOUT=*                                    
//SYSIN    DD *,SYMBOLS=EXECSYS                           
    COPY     DS(INCL(MY.TEST.ZFS              -           
                       ))      -                          
       TOL(ENQF) WAIT(1,1)     -                          
       CAT                     -                          
       ALLD(*) ALLX            -                          
       SPHERE                  -                          
       RENUNC(MY.TEST.ZFS              -                  
              MY.TEST.BACKUP.D&YYMMDD..ZFS) -             
       CANCELERROR                                        
/*                                                        

 

Equivalent in ansible without possibility to specify SYMBOLS=EXECSYS:

    - name: "ZFS backup"
      ibm.ibm_zos_core.zos_mvs_raw:
        program_name: adrdssu
        auth: true
        dds:
          - dd_input:
              dd_name: sysin
              content: |
                 COPY     DS(INCL(MY.TEST.ZFS  -
                                    ))      -
                    TOL(ENQF) WAIT(1,1)     -
                    CATALOG                 -
                    ALLD(*) ALLX            -
                    SPHERE                  -
                    RENUNC(MY.TEST.ZFS -
                            MY.TEST.BACKUP.D&YYMMDD..ZFS) -
                    CANCELERROR
          - dd_output:
              dd_name: sysprint
              return_content:
                type: text
      register: adrdssu_result
      failed_when: adrdssu_result.ret_code.code > 0

 

zos_mvs_raw is not able to resolve the variable value and fails.

It would be great to have a possibility work with symbols in in-stream datasets.

Idea priority Medium
  • Guest
    Reply
    |
    Dec 13, 2024

    Thank you for creating an idea Martin.

    Sharing my notes, while this idea is referring to an Ansible module zos_mvs_raw, the driving dependency is a ZOAU utlity 'mvscmd' and 'mvscmdauth' , but would benefit from supporting SYMBOLS. 

    Ansible (or users) would pass along the SYMBOLS and rely on ZOAU to do the substitution. 

    The symbols would need to be expanded before they are put into the temporary data set, so it can be other symbol services, not necessarily IAZSYMBL, this would be a great edition to the technical stacks.