• Product: Aleph
• Product Version: 20, 21, 22, 23
• Relevant for Installation Type:   All

Description:

The message "System can not generate login for login-type '00' " appears in the file-20 job log

Analysis:

The login-type ‘00’ is the z308 type ‘00’.   The PLIF input file almost always contains a USER-KEY-REC segment for the type 01 (barcode) and the type 02 (university ID or staff ID) and may contain other types, but does *not* normally contain a type 00 – which is the Aleph system ID for the patron.  {Normally this is assigned by the system from the z52 (util g/2) last- bor-id counter.}

But it *is* possible to include a value in a USER-KEY-REC type ‘00’ segment which the b_file_20 programs will then  use in the z308 type 00 they create, and also as the z303_rec_key.   

Resolution:

In the case where this "System can not generate login for login-type '00' " message was seen, the flat/sequential  PLIF input file was improperly formatted and the programs were finding blanks/spaces where the LOGIN-REC-LOGIN data should be.  (Note:  the text of this message is hard-coded in the ./butil/b_file_20_chk_edit_record program: “System can not generate login for login-type "  QUOTE Y308-KEY-TYPE .   It occurs when the Y308-KEY-TYPE is not 01 or 77** and when Y308-KEY-DATA = SPACES.)

Use util f/2/5/1 (“Display PLIF Records from Sequential File”) to diagnose the improper formatting of the flat/sequential PLIF input file, as described in the article ”Utility to view p_file_20 input records” linked to in Additional Information below.  In this particular case the records for the first patron in the file appeared in the utility as properly formatted, but the records for the second, third, etc., patrons had blanks where values were required, such as:

  ACTION........... 
  MATCH-ID-TYPE.... 
  MATCH-ID......... 
  ID-1............. 
  ID-2............. 

• ** See article "z308 key type 77"

Note to EL staff:  See Case 00187188 for the (rather lengthy) complete details.

In another case the site reported the following as the root problem:  “There was a data change in SAP, so it was partly null fields changing to contain spaces and missing line breaks between records. “