Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Examples

The following two examples, one for SF pubsets and one for SM pubsets, are intended to summarize the typical execution sequence from the user's point of view.

Example 1: SF pubset

The imported data pubset DAT1 (SF pubset) is buffered in the main memory.

/SHOW-MASTER-CATALOG-ENTRY CATALOG-ID=DAT1, INFORMATION=*USER —————————  (1) 
PUBSET DAT1: SINGLE-FEATURE, PUBRES-UNIT=FEE8, LOCAL-IMPORTED, NK-FORMAT
             EXTRA-LARGE-CATALOG
---- CURRENT PUBSET-PARAMETERS      ---------------------------------------- 
 MAXIMAL I/O LENGTH                   | 240 HP 
 ALLOCATION UNIT SIZE                 | 3   HP 
 PHYSICAL ALLOCATION                  | BY ADMINISTRATOR 
 SPEEDCAT MODE                        | SCA RUNNING 
---- CURRENT CACHE-CONFIGURATION    ---------------------------------------- 
 CACHE MEDIUM                         | VOLATILE 
 CACHE SIZE                           | 80 MB 
 DOUBLE BUFFERING                     | NO 
/SHOW-USER-ATTRIBUTES USER2, PUBSET=DAT1,INFORMATION=*PUBSET-ATTRIBUTES ——(2) 
SHOW-USER-ATTRIBUTES --- PUBSET DAT1 - USER USER2         2017-03-20 12:56:15
-----------------------------------------------------------------------------
USER-ID                  USER2           PUBLIC-SPACE-EXCESS     *NOT-ALLOWED
CODED-CHARACTER-SET     EDF03IRV        DMS-TUNING-RESOURCES    *CONCURRENT
NET-CODED-CHAR-SET      *ISO            PHYSICAL-ALLOCATION     *NOT-ALLOWED
                                      NET-STORAGE-USAGE       *ALLOWED
FILE-NUMBER-LIMIT         16777215      JV-NUMBER-LIMIT           16777215
LIMITED FILES                   27      JOB-VARIABLES                    0
PERM-SPACE-LIMIT          16777215      TEMP-SPACE-LIMIT        2147483647
PERM-SPACE-USED             424572      TEMP-SPACE-USED              12000
-----------------------------------------------------------------------------
SHOW-USER-ATTRIBUTES           END OF DISPLAY FOR USER USER2  ON PUBSET DAT1
/SHOW-FILE-ATTRIBUTES FILE-NAME=:DAT1:USERFILE ————————————————————————  (3) 
0000012000 :DAT1:$USER2.USERFILE
  ------------------------------- ORGANIZATION ------------------------------
  FILE-STRUC = NONE        BUF-LEN    = NONE        BLK-CONTR  = NONE
  IO(USAGE)  = READ-WRITE  IO(PERF)   = STD         DISK-WRITE = IMMEDIATE 
  REC-FORM   = NONE        REC-SIZE   = 0
  AVAIL      = *STD 
  WORK-FILE = *NO          F-PREFORM = *NK2         S0-MIGR = *ALLOWED
:DAT1: PUBLIC:      1 FILE  RES=     12000 FRE=     12000 REL=    12000 PAGES
/MODIFY-FILE-ATTRIBUTES FILE-NAME=:DAT1:USERFILE, 
     IO-ATTRIBUTES=*PARAMETERS(PERFORMANCE=*HIGH,
     USAGE=*READ),DISK-WRITE=*IMMEDIATE  —————————————————————————————— (4)

(1)

The command SHOW-MASTER-CATALOG-ENTRY enables the user to retrieve information on the cache activated for pubset DAT1, indicating whether a cache is active. In this example that is the case.

(2)

The SHOW-USER-ATTRIBUTES command allows the user to check his or her currently applicable pubset-specific authorization to process files using a cache. The displayed authorization indicates the highest permissible authorization (CONCURRENT(-USE)) for the user.

(3)

The command SHOW-FILE-ATTRIBUTES enables the user to check which file attributes he or she has already assigned to the USERFILE.

(4)

The user assigns the USERFILE the following performance-related file attributes:

  • The file is to be processed via a cache (PERFORMANCE=*HIGH). This specification will take effect, since the authorization CONCURRENT(-USE) has been entered for the user ID in the user catalog.

  • The request for high-performance file processing is to apply to read operations only (USAGE=*READ).

  • If the file is opened in write mode, the cache will not be used, because DISK-WRITE=*IMMEDIATE requires an always consistent write processing of the file.

Example 2: SM pubset

The volume set VS01 of the imported data pubset SMS1 (SM pubset) is buffered in the main memory.

/SHOW-PUBSET-DEFINITION-FILE PUBSET=SMS1,VOLUME-SET=VS01 ——————————————  (1) 
 -------------------------------------------------------------------------
 COMMAND: SHOW-PUBSET-DEFINITION-FILE
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
 PUBSET SMS1: TYPE=SYSTEM-MANAGED, VOLUMESETS=3, DEFAULT FILE FORMAT=NK2
 ---- VOLUME-SET INFORMATION --------- + ------------------------------------
 VOLUME-SET VS01: NORMAL-USE, NK2-FORMAT
---- GLOBAL ATTRIBUTES      --------- + -------------------------------------
 AVAILABILITY                         | STANDARD
 USAGE                                | WORK 
 FORMAT                               | NK2-FORMAT
 MAXIMAL I/O LENGTH                   | 240 HP
 ALLOCATION UNIT SIZE                 | 3   HP
 DRV-VOLSET                           | NO
 NEW FILE ALLOCATION                  | NOT RESTRICTED
 VOLUME SET ACCESS                    | NOT RESTRICTED
---- PERFORMANCE ATTRIBUTES --------- + -------------------------------------
 PERFORMANCE                          | STANDARD
 WRITE-CONSISTENCY                    | IMMEDIATE

(1)

The SHOW-PUBSET-DEFINITION-FILE command enables the user to retrieve information about the performance profile of volume set VS01 of pubset SMS1.

/SHOW-USER-ATTRIBUTES USER2,PUBSET=SMS1,INFORMATION=*PUBSET-ATTRIBUTES ———(2) 
SHOW-USER-ATTRIBUTES --- PUBSET SMS1 - USER  USER2        2017-03-21 11:53:55 
-----------------------------------------------------------------------------
USER-ID                 USER2         PUBLIC-SPACE-EXCESS     *NOT-ALLOWED
CODED-CHARACTER-SET     EDF03IRV        DMS-TUNING-RESOURCES    *CONCURRENT
NET-CODED-CHAR-SET      *ISO            PHYSICAL-ALLOCATION     *NOT-ALLOWED 
DEF-STORAGE-CLASS       *NONE           NET-STORAGE-USAGE       *ALLOWED
FILE-NUMBER-LIMIT         16777215      JV-NUMBER-LIMIT           16777215
LIMITED FILES                    1      JOB-VARIABLES                    0
                                   PERM-SPACE      TEMP-SPACE      WORK-SPACE
TOTAL-SPACE             LIMIT      2147483647      2147483647      2147483647
                        USED                0               0               3
S0-LEVEL-SPACE          LIMIT        16777215
                        USED                0
HIGH-PERF-SPACE         LIMIT        *MAXIMUM        *MAXIMUM        *MAXIMUM
                        USED                0               0               0
VERY-HIGH-PERF-SPACE    LIMIT        *MAXIMUM        *MAXIMUM        *MAXIMUM
                        USED                0               0               0
HIGH-AVAILABLE-SPACE    LIMIT               0
                        USED                0
-----------------------------------------------------------------------------
SHOW-USER-ATTRIBUTES          END OF DISPLAY FOR USER USER2    ON PUBSET SMS1 



(2)

The SHOW-USER-ATTRIBUTES command allows the user to check his or her currently applicable pubset-specific authorization to process files using a cache. The displayed authorization indicates the highest permissible authorization (CONCURRENT(-USE)) for the user. At the same time, the command indicates that the contingents for HIGH-PERF-SPACE and VERY-HIGH-PERF-SPACE have a value greater zero and that the user has not yet exceeded the contingents assigned to him or her.

/SHOW-PUBSET-FILE-SERVICES PUBSET=SMS1, SELECT=*BY-ATTRIBUTES(FILE-
ATTRIBUTES=*PARAMETERS( IO-
ATTRIBUTES=*PARAMETERS(PERFORMANCE=*HIGH,USAGE=*READ-WRITE), DISK-WRITE=*BY-
CLOSE))————————————————————————————————————————————————————————————————  (3) 
 WORK-F  AVAIL F-FORM   IO(PERF)  IO(USAGE) DISK-WRITE   SUPPORT-QUALITY
------+------+------+----------+----------+----------+-------------------
  YES    STD    NK2        HIGH READ-WRITE   BY-CLOSE           OPTIMAL
/CREATE-FILE FILE-NAME=:SMS1:USERFILE, IO-
ATTRIBUTES=*PARAMETERS(PERFORMANCE=*HIGH, USAGE=*READ-WRITE),DISK-WRITE=*BY-
CLOSE —————————————————————————————————————————————————————————————————  (4)

(3)

The SHOW-PUBSET-FILE-SERVICES command enables the user to verify whether pubset SMS1 offers the file service requested.

(4)

The user assigns the USERFILE the following performance-related file attributes:

  • The file is to be processed via a cache (PERFORMANCE=*HIGH). This specification will take effect, since the authorization CONCURRENT(-USE) has been entered for the user ID in the user catalog.

  • The request for high-performance file processing is to apply to both read and write operations (USAGE=*READ-WRITE).

  • By specifying DISK-WRITE=*BY-CLOSE, the user decides that the data are only stored in a consistent state at the time the file is closed. Therefore, the file can be processed in a cache in the main memory. Only files with easily restorable data should be given this attribute (e.g. a list file during a compilation), because a system error can lead to inconsistencies of these files.

Powered by Atlassian Confluence and Scroll Viewport.