CICS VSAM Transparency for z/OS, Version 1.2


Mapping an FBE

You can map an FBE in both manual and automated mapping dialogs. Figure 1 shows how to add an FBE using the manual mapping CICS® VT: Update field screen.

Figure 1. Mapping an FBE
 --------------------------- CICS VT: Update field ---------------------------
Command ===> ________________________________________________ Scroll ===> CSR 
                                                                              
DIM name       : ITEMFL                                                       
Creator        : CICSVT                                                     + 
Table          : HLL_ITEM                                                   + 
Data set length: 00080                                                        
                                                                              
Field name . . . . . . : F07                                                  
Field length . . .  ===> 00003              (In bytes)                        
Field type . . . .  ===> C                  (C,P,U,F,H,B)                     
Column name  . . .  ===> ITEM_SUPP_CODE................ + (Look-up available) 
Starting position   ===> 00036              ("1" = Beginning of data set)     
Picture or FBE . .  ===> EXITL=SUPPFBE_____________  (example HH.XX.SS.NNNNNN)
                                                          (or MMDDYY)         
                                                          (or EXITx=exit name)
Parameters . . . .  ===> __________________________  Optional user parameters 
Special function .  ===> ___                ("KEY", "PTH", "BKY", or blank)   
Mapped from table   ===> P                  ("P"=Prim, "X"=Not mapped)        
Build order  . . .  ===> 00007              ("1"=first, "2"=second and so on) 
                                                                              
                                                                              
Press: Enter=Update  PF3=Exit  PF1=Help                                                                             
 

Figure 1 shows that an LE/370 FBE called SUPPFBE has been mapped for the field F07.

In some cases, virtually the entire record area may be built by a combination of an FBE and an IRD. This may be for a file containing multiple record types where the only field that is common to each record type is the key field. The mapping shown in Figure 2 represents a complex file that is managed by the LE/370 FBE MULTFBE and IRD MULTIRD.

Figure 2. Mapping a complex file
 ------------------- CICS VT: List of fields for APPLCTL    -- Row 1 to 7 of 7 
Command ===> ________________________________________________ Scroll ===> CSR  
                                                                               
VSAM file type : KSDS     Creator   : CIRSP                                  + 
Data set length: 00263    Table name: TB_APPLCTL                             + 
                                                                               
Actions: S Display, U Update, I Insert, D Delete                               
                                                                               
A Field    Bytes Start Type DB2 column name                  Exit     Pic Par  
- -------- ----- ----- ---- ------------------------------   -------- --- ---  
_ KY       00017 00001   C                                 +                   
_ OBJECT   00006 00001   C  OBJECT_ID                      +                   
_ RECTYPE  00003 00007   C  REC_TYPE                       +                   
_ USERID   00008 00010   C  USER_ID                        +                   
_ FILLER   00233 00018   C                                 + MULTFBE           
_ ULSTCHG  00008 00251   C  USER_ID_LAST_CHG               +                   
_ CHGDTE   00005 00259   P  LAST_CHG_DATE                  + DATEFBE           
******************************* Bottom of data ********************************

The field called FILLER refers to an area in the VSAM record that is redefined with four different record types. The other mapped fields are common to each record.

MULTFBE and MULTIRD are written in COBOL and are explained in Record level reengineering.

The FBE DATEFBE is explained in Reformatting a date field.

Note that the field names shown in Figure 2 are for illustration purposes. The actual field names used in manual mapping are generated.



Concept topic


Last updated: November 9, 2012 20:43:56