Set VST server definitions:

1. Enter the following:

   vim $alephe_root/aleph_start.private

   Requests are stored in the library defined as vst_library. By default, this is the USR00 library (as defined in aleph_start). If you want to use another library, define it in aleph_start.private as follows:

   setenv vst_library XXXNN

   Generally you should use the USR00. So, there is no additional entry in aleph_start.private that is necessary.
   The server for the data replication interface (VST server) runs by default under port 522x. If you want to use another port, you may enter it in aleph_start.private:

   setenv VST_SERVER_PORT nnnn

   For example:

   setenv VST_SERVER_PORT 4711

2. Enter the following:

   vim $alephe_tab/tab_low_group

   In tab_low_group, the local catalog IDs are defined. Z115 records are only created if a local catalog ID is present. A local catalog ID may represent 1 to n sublibrary codes. For every local system for which you want to generate Z115 messages, you need to define a sublibrary code.

   If a library wants to trigger a Z115 message to the VST server regardless of the BIB's LOW field, set the tab_low_group as follows:

   ! 1   2     3     4     5     6     7
   !!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!!!!!-! 
   ALMA  ALL

   The above setup results in a message each time a BIB record is updated, without any dependency in LOW tag.

   For example:

   ! 1   2     3     4     5     6     7
   !!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!
   VST01 LOC28 VST02 LOC69 LOC70 LOC75
   VST05 LOC75 VST06 VST06
    

   The VST02 local catalog ID contains several sublibrary codes. If you correct a BIB record that contains at least one ownership verification from the VST02 list, a Z115 record for the correction is created. If the first ownership verification is generated for a BIB record or the last one is deleted, a Z115 record for creation or deletion is generated.
   When correcting series or collective titles, Z115 records are created for all local catalog IDs. This applies to authority records as well. For holdings records, the table tab_low_group acts as concordance, since there is always one sub library code (OWN) per holdings record.
   For Alma:

   ! 1   2     3     4     5     6     7
   !!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!!!!!-! 
   ALMA  #####

   For libraries that use a parent-child link between records, you can configure that when a child BIB record is updated, a Z115 is created for its parent, in addition to the child's Z115 record.
   In order to activate the above functionality, column 7 in tab_low_group should be set to 'Y'.

   For example:

   ! 1   2     3     4     5     6     7
   !!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!!!!!-! 
   ALMA  #####                         Y

   Parent record links are based on the definitions in the ./[bib_library]/tab/tab_relink_link table. Therefore, in order to activate the Send Parent functionality, tab_relink_link should be defined with all parent links.

   For example:

   ! 1   2  3  4   5   6  7  8 9
   !!!!!-!-!!!-!-!!!!!-!-!!!-!-!
   010## a 001           DN    Y
   

3. Enter the following:

   vim $alephe_unicode/tab_character_conversion_line

   When sending messages via the VST server, a character conversion may be activated. The server sends the data - if no conversion is defined - as UNICODE characters (UTF8). You assign a conversion with the entry "UTF_TO_VST".
   For example:

   !!!!!!!!!!!!!!!!!!!!-!!!!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!-! 
   UTF_TO_VST           ##### L line_utf2line_sb               unicode_to_8859_1    Y
   

   If required, further conversion programs and tables may be implemented.
4. Activate the vst library.
   Requests are generated only if this function is activated in the vst library. In order to do this, you need to add the following entries in the file_list of the VST library and initialize the Z115 table via UTIL A 17/1.

   TAB z115 100K,128K,128K,128K,128K,128K 0K ts0,TS1D,TS1D,TS1D,TS1D,TS1D
   IND z115_id 100K,128K,128K,128K,128K,128K 0K ts1,TS1X,TS1X,TS1X,TS1X,TS1X

   The size of the table depends on the number of expected requests. Requests are not automatically deleted. They should be manually deleted in regular intervals or archived.
   In addition, the counter "last-vst-number" needs to be defined via UTIL G / 2. No prefix is assigned, and leading zeros must not be suppressed.
   As soon as Z115 is established and the related counter is defined, requests for the local catalog IDs from tab_low_group are written. Restart VST server.

Set Z39.50 definitions Aleph z39_server

1. Verify that the port is correct under $alephe_tab/z39_server/z39_server.conf.
    
2. MAB environment:
       Change 'Z39' staff to ADMIN (User library) and add permissions for 'MAB01' library (Allow all common tab).
   
   For USMARC environment:
       Change 'Z39' staff to ADMIN (User library) and add permissions for 'USM01' library (Allow all common tab).
    
3. In order to return UTF via Z39, change in ./alephe/tab/z39_server/z39_server_MAB01.conf (or z39_server_USM01.conf ) the following:
   MAB environment:
   The MAB2MARC section should have a matching section in tab_expand, and the MB2MC section should have a matching section in tab_fix.
   • out-record-syntax USMARC
   • out-record-format USMARC
   • out-record-char-conv
   • out-record-expand MAB2MARC
   • out-record-fix MB2MC
   USMARC environment:
   The Z39_SERVER section should have a matching section in tab_expand, and the "Z39_server" section should have a matching section in tab_fix / tab_expand. .
   • out-record-syntax USMARC
   • out-record-format USMARC
   • out-record-char-conv
   • out-record-expand Z39_SERVER
      
4. Optionally, (MAB environment only) - define a new base for Alma Z39.50 searches that use the new MB2MC conversion in order to keep the original settings (old MAB -> MARC conversion). See details in the sections below: Convert MAB To MARC .
    
5. Optionally, (USMARC environment) - define a new base for Alma Z39.50 searches that use a new expand "Z39_SERVER" that adds the 003 field with a predefined code, and 035 field that contains the System number from 001 + Prefix from 003. See Expand - Add 003 and 035.

Convert MAB To MARC: (MAB environment only)

1. Add a new section in ./[bib_library]/tab_expand similar to the following example:

   !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> 
   MAB2MARC   expand_doc_bib_bib_mab2marc    DOWN-MAX=10
   MAB2MARC   fix_doc_clear                  DUP-FLD=Y
   

2. Add a new section in ./[bib_library]/tab_fix (For Alma) entry similar to the following example:

   !!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
   MB2MC fixexp_docx_parallel           INIT
   MB2MC fixexp_docx_parallel           COPY,PTR-FROM=0,PTR-TO=I
   MB2MC expdoc_43obv_bib_bib_mab2marc  DN-MAX=10,SRD-MAX=10
   MB2MC fix_doc_mab                    FUNC=OUTPUT,FILE=alma_obvsg.tab_fix_mab.bib_mab2marc
   MB2MC fix_doc_mab                    FILE=alma_obvsg.tab_fix_mabaseq.bib_mab2marc
   MB2MC fix_doc_clear                  DUP-FLD=Y
   MB2MC fix_doc_43obvos_recode_ind2tag
   MB2MC fixexp_docx_parallel           COPY,PTR-FROM=0,PTR-TO=B
   MB2MC fixexp_docx_parallel           FIXROUT,MBPR1,PTR-FROM=0,PTR-TO=H
   MB2MC fixexp_docx_parallel           CAT,PTR-FROM=0,PTR2FROM=H
   MB2MC fixexp_docx_parallel           CAT,PTR-FROM=0,PTR2FROM=H
   MB2MC fixexp_docx_parallel           FIXROUT,MBPR2,PTR-FROM=0,PTR-TO=W
   MB2MC fixexp_docx_parallel           CAT,PTR-FROM=0,PTR2FROM=W
   MB2MC fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_mab2marc.main
   MB2MC fixexp_docx_parallel           FIXROUT,MBOS1,PTR-FROM=B,PTR-TO=1
   MB2MC fixexp_docx_parallel           PARFUNC,copyfld,"LDR,LDRMC",PTR-FROM=0,PTR-TO=1
   MB2MC fixexp_docx_parallel           FIXROUT,MBOS2,PTR-FROM=1,PTR-TO=2
   MB2MC fixexp_docx_parallel           PARFUNC,43obvos_catlink,PTR-FROM=0,PTR2FROM=2,PTR-TO=0
   MB2MC fix_doc_mab2marc_synind_880lnk
   MB2MC fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_mab2marc.post_01
   MB2MC fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_mab2marc.upd_lnkidn
   MB2MC fixexp_docx_parallel           FIXROUT,MBNOM,PTR-FROM=I,PTR-TO=M
   MB2MC fixexp_docx_parallel           CAT,PTR-FROM=0,PTR2FROM=M
   MB2MC fix_doc_sort_marc21            USECODE=Y
   MB2MC fix_doc_clear                  DUP-FLD=Y
    
   MBPR1 fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_mab2marc.pre_h_fields
   MBPR2 fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_mab2marc.pre_wk_fields
    
   MBOS1 fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_mab2marc.os1
   MBOS2 fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_mab2marc.os2
    
   MBNOM fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_mab2marc.nomapp
   

   In MAB environment - this fix routine should match the fix routine used in $alephe_tab/z39_server/z39_server_MAB01.conf for the line:

   out-record-fix MB2MC

3. In MAB environment Define user-specific values via the global variables table.
   The name of the table in $data_tab is tab_globalvar_convtb.m2m.
   Copy the table ./mab01/tab/ttt_49bvb.tab_globalvar_convtb.m2m to ./[bib_library]/tab/tab_globalvar_convtb.m2m and change the ISIL-Code user.

Convert MARC to MAB: (MAB environment only)

1. Add a new section in ./[bib_library]/tab_expand and/or ./[bib_library]/tab_fix (For Alma, in MAB01).
   The section is similar to the following example (only fix-lines) :

   !!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
   MC2MB fix_doc_remove_punctuation_usm
   MC2MB fix_doc_convtb                 FILE=ttt.tab_fix_convtb.bib_marc2mab.49kobv_p0_tt_pp
   MC2MB fix_doc_convtb                 FILE=ttt.tab_fix_convtb.bib_marc2mab.49kobv_p1
   MC2MB fix_doc_convtb                 FILE=ttt.tab_fix_convtb.bib_marc2mab.49kobv_p2
   MC2MB fix_doc_clear                  DUP-FLD=Y
   MC2MB fix_doc_overlay                TMARC2MABI
   MC2MB fix_doc_sort_mab
   

2. Set the merge of the input record and the DB record by adding a merge section as defined for fix_doc_overlay routine in tab_fix.
   See the template option in ./mab01/tab/addon_ttt_m2m.bib.tab_merge table.
   For example, for the above TMARC2MABI, add the following in ./[bib_library]/tab/tab_merge :

   ! 1        2                               3
   !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
   TMARC2MABI merge_doc_overlay              08
   

3. In ./[bib_library]/tab/tab_merge_overlay, add the merge definitions. The merge set should match the merge set defined in tab_merge.
   See the template option in the ./mab01/tab/addon_ttt_m2m.bib.tab_merge_overlay table.
   For example, for the above merge set '08' add the following lines:

   !1 2 3 4
   !!-!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   ...
   !
   08 1 N #####
   08 1 Y CAT##
   08 1 Y LOW##
   08 1 Y OWN##
   08 2 Y #####

   When the LOW field is defined in ./[bib_library]/tab/tab_cat_hidden_fields as a hidden field, remove the following line from the definition of tab_merge_overlay above: 

    

   08 1 Y LOW##
   

Expand - Add 003 (Prefix) and 035 (System number + Prefix) (USMARC environment)

!
Z39_SERVER expand_doc_sysno
Z39_SERVER fix_doc_do_file_08             alma.fix
Z39_SERVER fix_doc_create_035_1
!Z39_SERVER fix_doc_create_035

!   2   3  4  5   6    7                 8                           9
!-!!!!!-!!-!-!!!-!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
1 FMT                      DELETE-FIELD
! Handles system number etc.
1 003##                    DELETE-FIELD
2 035##                    DELETE-FIELD-COND              Y,$$a(ALM)
2 LDR                      ADD-FIELD                      003  ,L,ALM
        

Configure update-doc-alma X-service:

1. In MAB environment : To handle MARC-MAB conversion in 'update-doc-alma' X-Service , add fix routines for section 'ALMA1' in ./[bib_library]/tab/tab_fix.
   Example of 'MARC to MAB' conversion for a MAB-ALEPH-Central Catalog:

   !!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
   ALMA1 fixexp_docx_parallel           INIT
   ALMA1 fix_doc_clear                  DUP-FLD=Y
   ALMA1 fix_doc_mab2marc_rm_punct_usm
   ALMA1 fixexp_docx_parallel           COPY,PTR-FROM=0,PTR-TO=M
   ALMA1 fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_marc2mab.pre_01
   ALMA1 fixexp_docx_parallel           COPY,PTR-FROM=0,PTR-TO=O
   ALMA1 fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_marc2mab.49dnb_p0_tt_pp
   ALMA1 fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_marc2mab.49dnb_p1
   ALMA1 fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_marc2mab.49dnb_p2
   ALMA1 fix_doc_convtb                 FILE=alma_obvsg.convtb.bib_marc2mab.post_01
   ALMA1 fixexp_docx_parallel           FIXFUNC,fix_doc_convtb,"FILE=alma_obvsg.convtb.bib_marc2mab.osc",PTR-FROM=O,PTR-TO=O
   ALMA1 fixexp_docx_parallel           CAT,PTR-FROM=0,PTR2FROM=O
   ALMA1 fixexp_docx_parallel           FIXFUNC,fix_doc_convtb,"FILE=alma_obvsg.convtb.bib_marc2mab.nomapp",PTR-FROM=M,PTR-TO=M
   ALMA1 fixexp_docx_parallel           CAT,PTR-FROM=0,PTR2FROM=M
   ALMA1 fix_doc_char_conv_z            GND-UTF-TO-UTF
   ALMA1 fix_doc_clear                  DUP-FLD=Y
   ALMA1 fix_doc_sort
   ALMA1 fix_doc_overlay                ALMA1MC2MB
   ALMA1 fix_doc_sort
   

   The fix section can be sent as a parameter to the X-service. In this case, each member should have a section defined in tab_fix with the above lines.
   To enable the loading of records with long fields (over 2000 characters), add the following line in . /alephe/aleph_start.private: 

   setenv  ENABLE_LONG_FIELDS  Y

2. To set the merge of the input record and the DB record, add a merge section as defined for fix_doc_overlay routine in tab_fix. Each member can have a different merge section.
   For example, for the above ALMA1MC2MB, add the following in ./[bib_library]/tab/tab_merge:

   !   1                   2                               3
   !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
   ALMA1MC2MB merge_doc_overlay              AA
   

3. In ./[bib_library]/tab/tab_merge_overlay, add the merge definitions. The merge set should match the merge set defined in tab_merge.
   For example, for the above merge set AA, add the following lines:

   !1 2 3          4
   !!-!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   ...
   ! For Alma X-service
   AA 1 N #####
   AA 1 Y CAT##
   AA 1 Y OWN##
   AA 1 Y OSC##
   AA 2 Y #####
   

Configure the load holdings information (Bib record LOW field)

1. To handle deletion of LOW field,
   add the following line in ./[bib_library]/tab/tab_fix with the required section: 

   !!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
   LOWRM fix_doc_do_file_08 delete_low_fields

2. To delete the LOW field via a fix routine, verify that the ./[bib_library]/tab/import/delete_low_fields table contains the following line: