GETBLDMP—Retrieve Build Map Information

The GETBLDMP service retrieves the Build Map information associated with an SCLM-controlled member into an ISPF table. The information is retrieved from the accounting file defined in the project definition for the group specified to the service. The service can search up the hierarchy for the member, or retrieve the information for a specific member. See ISPF variables for a list of the variables updated by this service.

Command invocation format


>>-FLMCMD--GETBLDMP,project--,-+---------+--,group--,type------->
                               '-prj_def-'                  

>--,member--,bmap_table--,-+---------+-------------------------><
                           '-dd_msgs-'

Call invocation format


>>-lastrc--:=--FLMLNK('GETBLDMP',sclm_id--,group--,type--------->

>--,member--,bmap_table--,$msg_array);-------------------------><

ISPF interface panel

Figure 1. GETBLDMP Service panel

   Menu  SCLM  Utilities  Help
 ──────────────────────────────────────────────────────────────────────────────
                   SCLM FLMCMD GETBLDMP Service - Entry Panel

 SCLM Library:
    Project . . . SCLMTEST
    Alternate . .         
    Group . . . . DEV1    
    Type  . . . . SOURCE  
    Member  . . .         

 DD Name for output data set:
    Error message data set           (Blank to write messages to the terminal)








 Command ===>                                                                  
  F1=HELP      F2=          F3=END       F4=DATASETS  F5=FIND      F6=CHANGE
  F9=SWAP     F10=LEFT     F11=RIGHT    F12=SUBMIT

Parameters

project

The project name. The maximum parameter length is 8 characters. This parameter is used for FLMCMD only.

prj_def

The project definition name. It defaults to the project name. The maximum parameter length is 8 characters. This parameter is used for FLMCMD only.

sclm_id

An SCLM ID associated with a given project and project definition. The INIT service generates the SCLM ID. The maximum parameter length is 8 characters. This parameter is used for FLMLNK only.

group

The group associated with the accounting record. The maximum parameter length is 8 characters.

type

The type associated with the accounting record. The maximum parameter length is 8 characters.

member

The member under SCLM control. The maximum parameter length is 8 characters. You can specify an individual member, an asterisk for all of them, or a valid pattern.

bmap_table

The name of the ISPF table to contain the build map entries. The table must be open before calling the GETBLDMP service. A TBADD is performed for each build map record.

The following ISPF variables must be used in the table definition in order to have their value stored in the table. All of the variables are optional and only the variables required need to be specified:

ZSBMGRP: Group name where build map was located
ZSBMTYP: The type associated with the accounting record for which the build map was requested. This will be the same as was specified in the type parameter.
ZSBMMEM: Member name(s) of build map entries that match the pattern specified in the member parameter.
ZSBKWRD: entry type. For example the keyword used in the ARCHDEF or language definition, such as SINC, OBJ, and LOAD.
ZSBGRP: Build map entry group name. Group where the account record for the build map entry is stored in SCLM.
Note : If this parameter is specified in the table, then the account records for each build map entry will be searched to locate the group where the account record exists. If a wildcard is used for member, or the build map is large, this call may take some time.
ZSBMEM: member name
ZSBTYPE: member type
ZSBDATEn: build date (in YYYYMMDD format)
ZSBTIME: build time (in HHMMSS format)
ZSBVER: version
ZSBLINE: unformatted data line (72 characters)

The maximum parameter length is 8 characters (except for ZSBLINE).

dd_msgs

The ddname indicating the destination of the messages generated by the GETBLDMP service. If you specify a blank ddname, SCLM routes the GETBLDMP messages to the default output device, such as your terminal. Otherwise, before you call the GETBLDMP service, you must allocate the ddname. The following attributes should be used: RECFM=F, LRECL=80, BLKSIZE=80. The maximum parameter length is 8 characters. This parameter is used for FLMCMD only.

$msg_array

An output parameter pointing to the message array. See Pointer parameter descriptions for more information about $msg_array. This parameter is used for FLMLNK only.

Example of an AUTHCODE report

This sample REXX code is an example of how to invoke the GETBLDMP service.

/* REXX */

   address ispexec
   'CONTROL ERRORS RETURN'
   'TBEND   BMAPTABL'
   'CONTROL ERRORS CANCEL'
   tbnames = 'NAMES(ZSBMGRP ZSBMTYP ZSBMMEM ZSBKWRD ZSBMEM ZSBTYPE
                    ZSBDATE ZSBTIME ZSBVER  ZSBLINE ZSBGRP)'
   'TBCREATE BMAPTABL' tbnames 'NOWRITE'
   'TBVCLEAR BMAPTABL'

   parmbmap = 'ADMIN10,ADMIN10,DEV1,COBOL,RDBK*'
   Address TSO 'FLMCMD GETBLDMP,'||parmbmap||',BMAPTABL'
   Say 'Return code from Build Map lookup = 'rc
   If RC < 5 Then
   Do
      'TBTOP  BMAPTABL'
      'TBSKIP BMAPTABL'

      Say ''
      Say 'BM Group BM Type  BM Memb ' ,
          'Keyword  Member   Type     Group    Date/Time Modified  Version'
      Do While (RC = 0)
         Say SUBSTR(ZSBMGRP,1,8) SUBSTR(ZSBMTYP,1,8) SUBSTR(ZSBMMEM,1,8) ,
             SUBSTR(ZSBKWRD,1,8) SUBSTR(ZSBMEM,1,8) SUBSTR(ZSBTYPE,1,8),
             SUBSTR(ZSBGRP,1,8) ZSBDATE'  'ZSBTIME '  ' ZSBVER '  '
         'TBSKIP BMAPTABL'
      End
      'TBEND BMAPTABL'
   End

This example builds the temporary ISPF table BMAPTABL with all of the available parameters. The service call is invoked for COBOL members beginning with RDBK, starting at the DEV1 group in the hierarchy. Once complete the temporary ISPF table is read to list out the build map entries.

Here is the output:

Return code from Build Map lookup = 0

BM Group BM Type  BM Memb  Keyword  Member   Type     Group  Date/Time Modified Version
DEV1     COBOL    RDBKC02  SINC     RDBKC02  COBOL    DEV1   20070625  155226   1
DEV1     COBOL    RDBKC02  OBJ      RDBKC02  OBJ      DEV1   20070625  155357   1
DEV1     COBOL    RDBKC02  LIST     RDBKC02  LIST     DEV1   20070625  155357   1
DEV1     COBOL    RDBKC02  OUT1     RDBKC02  DBRM     DEV1   20070625  155357   1
DEV1     COBOL    RDBKC02  I1*      ORDRSET  COPYBOOK TEST   20070607  114654   1
DEV1     COBOL    RDBKC02  I1*      RDBKTB01 COPYBOOK TEST   20070522  165926   1
TEST     COBOL    RDBKC01  SINC     RDBKC01  COBOL    DEV1   20070612  143325   3
TEST     COBOL    RDBKC01  OBJ      RDBKC01  OBJ      TEST   20070625  155347   14
TEST     COBOL    RDBKC01  LIST     RDBKC01  LIST     TEST   20070625  155347   14
TEST     COBOL    RDBKC01  OUT1     RDBKC01  DBRM     TEST   20070625  155347   13
TEST     COBOL    RDBKC01  I1*      ORDRSET  COPYBOOK TEST   20070607  114654   1
TEST     COBOL    RDBKC01  I1*      RDBKTB01 COPYBOOK TEST   20070522  165926   1
TEST     COBOL    RDBKC01  I1*      RDBKDC01 DCLGEN   TEST   20070612  143307   1

Return codes

Additional special services messages are written to the FLMMSGS ddname. See SCLM service messages for more information.

Other return codes might be produced by the FLMCMD or the FLMLNK processor. See SCLM service return codes for more information.

Possible return codes are:

0: Normal completion. A build map record was found that exactly matched the specified criteria and the information was stored successfully.
4: Normal completion. A build map record was found at a higher level. The information was stored successfully.
8: Error completion. No account record was found for the specified member.
12: Error completion. Refer to the messages for more information.