when trying to export records using the marc_export script we get 'Can't use an undefined value as an ARRAY reference at /openils/bin/marc_export line 386.'

[Anoop Atre]

This likely affects all version of Evergreen, tested on 2.4 and 2.3.6, gmcharlt strongly suspects that it was introduced by b1e6cde52 (bug 1022582)

When trying to export records using the marc_export script we get 'Can't use an undefined value as an ARRAY reference at /openils/bin/marc_export line 386.'

Using diagnostics:

opensrf@test:/tmp$ cat /tmp/list_of_ids | /openils/bin/marc_export > /tmp/output_data
Subroutine section_pkg redefined at (eval 1496) line 4 (#1)
    (W redefine) You redefined a subroutine. To suppress this warning, say

        {
     no warnings 'redefine';
     eval "sub name { ... }";
        }

Use of uninitialized value $required in string eq at
 /usr/local/share/perl/5.10.1/OpenILS/Utils/Fieldmapper.pm line 86 (#2)
    (W uninitialized) An undefined value was used as if it were already
    defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
    To suppress this warning assign a defined value to your variables.

    To help you figure out what was undefined, perl will try to tell you the
    name of the variable (if any) that was undefined. In some cases it cannot
    do this, so it also tells you what operation you used the undefined value
    in. Note, however, that perl optimizes your program and the operation
    displayed in the warning may not necessarily appear literally in your
    program. For example, "that $foo" is usually optimized into "that "
    . $foo, and the warning will refer to the concatenation (.) operator,
    even though there is no . in your program.

Use of uninitialized value $controller in split at
 /usr/local/share/perl/5.10.1/OpenILS/Utils/Fieldmapper.pm line 170 (#2)

Can't use an undefined value as an ARRAY reference at /openils/bin/marc_export line 388.

Exports Attempted : 1
Exports Completed : 0
Overall Speed : 0
Total Time Elapsed: 0.116323947906494 seconds

[Mark Cooper (markchristophercooper)]

As the one possibly responsible I'll look into this (hopefully) today.

I plan to try exporting some records using a 2.4.0 system using concerto and a 2.3.2 system using our local data. Both systems have the suspect branch applied.

Depending on what happens I'll pick out the changes introduced by the branch and repeat the test -- will update when I have some results.

Mark.

[Mark Cooper (markchristophercooper)]

Indeed -- broken on 2.3.2 / 2.4.0. Here's a proposed fix to test:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=6923168f68ecf504c8703aea610a173345850e5b

[Galen Charlton (gmc)]

Works for me. Pushed to master and rel_2_3. Thanks, Mark!

[Galen Charlton (gmc)]

And pushed to rel_2_4

[Alan Simon (qp-simen-44)]

I was the original reporter of this bug to Equinox. The patches correct the problem in my 2.3.6 system.

[Tony Bandy (tonyb-y-deactivatedaccount)]

Hi all,

It could just be me, but after applying the patch, I still could not get things to run. I ended up dropping back to 2.1.2 and running the marc_export that way. (OK to do that you think?)

The 2.1.2 documentation did not reference the marc_export.in file, only the marc_export, but after making the change to marc_export in my 2.3.6 directory, I still could not get things to work as they should....

--Tony

[Mark Cooper (markchristophercooper)]

Hi Tony,

I can't replicate the issue since the fix, everything seems fine to me. bshum in IRC also indicated that things are working for him. Are you sure you changed the code correctly? Perhaps you can show us your marc_export script?

Mark