1 / 14

z/OS FNA Revealed and Exposed - File Name Transformation Guide

This guide provides a comprehensive overview of the file name transformation in z/OS FNA, covering history, POSIX, syntax, examples, and more.

Download Presentation

z/OS FNA Revealed and Exposed - File Name Transformation Guide

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. z/OS FNA Revealed and Exposed Phil Veal Senior Principal Support Engineer Bug Diagnosis and Escalations

  2. Agenda <Insert Picture Here> • History • File name transformation • POSIX • Syntax • Examples

  3. File Name Augmentation • A brief history • Available since MPM days (1980’s) • Pre-dates UNIX System Services and zFS/HFS • Originally used Oracle C runtime library syntax • Since Oracle 9.2.0, uses IBM LE syntax • Backwards compatibility is maintained • ORA$ENV: ORA_RTL_COMPAT=ON (default)

  4. File Name Transformation Oracle utilities use simple file specifications E.g. myquery.sql, myquery.lst The native MVS file system uses datasets E.g. MYGROUP.LIB.SQL(MYQUERY), &&SPOOLOUT Question: How to convert a file name to a dataset name automatically? Answer: ORA$FNA

  5. POSIX(OFF) versus POSIX(ON) • LE runtime parameter • POSIX(ON) • For UNIX System Services environment • LE enclave uses POSIX semantics • POSIX(OFF) • Default for traditional MVS batch and TSO environments • LE enclave uses non-POSIX semantics • Simple file names are interpreted as datasets or files, as appropriate

  6. File Name Syntax • Old MPM syntax - • /DD/name • /DSN/name • OSDI syntax - • //DD:name • //’name’ • //SYSOUT:class • Old syntax still accepted, but not recommended • May be disabled via ORA_RTL_COMPAT (default ON)

  7. FNA Syntax //ORA$FNA DD DSN=…|PATH=… FSA( FTYPE(extension) FNAME(new name) FATTR(attribute string) )

  8. FTYPE • File name type/extension • Logical data type identifier • Defaults defined by Oracle tools • Usually 3 characters • Examples – • .sql, .plb, .lst, .ctl, .log, .dmp • Can be user defined

  9. FNAME • New transformed file name • Original file specification may be included using “+” • Example 1: FNAME(‘MYLIB.SQL(+)’) • stuff.sql -> MYLIB.SQL(STUFF) • Example 2: FNAME(‘MYGROUP.+’) • stuff.sql -> MYGROUP.STUFF.SQL • PROFILE PREFIX (TSO) or USERID (batch) may be included using “*” • E.g. FNAME(“//’*.LIB.SQL(+)’”)

  10. Examples FSA( FTYPE(SQL) FNAME(‘LIB(+)’) ) LIB.SQL(STUFF) stuff.sql FSA( FTYPE(SQL) FNAME(‘//DD:SQL(+)’) ) //DD:SQL(STUFF) stuff.sql FSA( FTYPE(LST) FNAME('//SYSOUT:X') ) //SYSOUT:X SPOOL report

  11. FATTR • File attribute assignment • Output only • Must begin with a semicolon • Keywords – • RECFM=V(B)|F(B) etc. • LRECL=record length • BLKSIZE=block size • SPACE=(units,(primary,secondary,directory blocks)) • Example - • FATTR(';space=(trk,(2,1)),recfm=VBA,lrecl=137,blksize=0')

  12. Questions?

  13. <Insert Picture Here> https://metalink.oracle.com/ Forums: IBM z/OS Platform Phil.Veal@oracle.com

More Related