Open-source Languages & Tools for z/OS

Expand all | Collapse all

Error after customizing .profile and .bashrc for miniconda install

Jump to Best Answer
  • 1.  Error after customizing .profile and .bashrc for miniconda install

    Posted 05-13-2021 17:58

    Hello: I've installed miniconda and am now trying to get my environment customized for it. I made the updates to .profile and .bashrc and restarted my ssh session. When I sign back in, I get this:

    bash: $'{@\202\201\242\210\231\203@\206\211\223\205\025{@\203\226\225\243\205\225\243@\206\226\231@\331\226\203\222\205\243@\224\211\225\211\203\226\225\204\201\025K@a\244a\242\205\244\202\205\231\243a\243\226\226\223\242a\231\226\203\222\205\243a\224\211\225\211\203\226\225\204\201a\205\243\203a\227\231\226\206\211\223\205K\204a\203\226\225\204\201K\242\210\025': command not found

    Here's my .profile (miniconda is installed in /u/SEUBERT/tools/rocket/miniconda

    echo 'Running .profile...'
    # export PATH=/u/SEUBERT/tools/ibm/python/cyp/v3r8/pyz/bin:/usr/bin:$PATH
    export PATH=/usr/bin:/bin:./usr/sbin:/usr/lpp/java/J8.0_64/bin:/usr/lpp/IBM/cobol/igyv6r2/bin:/usr/lpp/IBM/pli/v5r2/bin
    export LIBPATH=/u/SEUBERT/tools/ibm/python/cyp/v3r8/pyz/lib:$LIBPATH
    export _BPXK_AUTOCVT='ON'
    export _CEE_RUNOPTS='FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)'
    export _TAG_REDIR_ERR=txt
    export _TAG_REDIR_IN=txt
    export _TAG_REDIR_OUT=txt
    SHELL=/u/SEUBERT/tools/rocket/miniconda/bin/bash
    exec $SHELL


    What do I have wrong here? I tried adding the miniconda bin directory to the path but it still fails.

    Help?



    ------------------------------
    Bill Seubert
    Solutions Architect
    AWS
    ------------------------------


  • 2.  RE: Error after customizing .profile and .bashrc for miniconda install

    Posted 05-13-2021 18:36
    What is in your .bashrc?

    ------------------------------
    LionelDyck <><
    https://github.com/zigi
    https://github.com/lbdyck
    ------------------------------



  • 3.  RE: Error after customizing .profile and .bashrc for miniconda install

    Posted 05-13-2021 18:43
    Hey, Lionel - great to hear from you!

    This is in .bashrc, but it isn't getting fired, since that error message is coming from bash itself. I put an echo ".bashrc is running" in the script but it's not showing up.

    # bashrc file
    # content for Rocket miniconda
    echo "bashrc is running"
    . /u/seubert/tools/rocket/miniconda/etc/profile.d/conda.sh

    ------------------------------
    Bill Seubert
    Solutions Architect
    AWS
    ------------------------------



  • 4.  RE: Error after customizing .profile and .bashrc for miniconda install
    Best Answer

    ROCKETEER
    Posted 05-14-2021 05:31
    Edited by Dave Andrews 05-14-2021 09:40

    Hi Bill, 

    I suppose, the .bashrc file tag have no match with encoding. More likely you have .bashrc file with EBCDIC (IBM-1047)  content and latin-1 (ISO8859-1) tag.

    To fix the tag:

    chtag -tc IBM-1047 .bashrc

    You can check the tag of the file by 'ls -T' command.

    ls -T .bashrc



    ------------------------------
    Sergey Rezepin
    Rocket Software
    ------------------------------



  • 5.  RE: Error after customizing .profile and .bashrc for miniconda install

    Posted 05-14-2021 09:38
    Good call, Sergey - that was it.

    I created .bashrc with vi while connected thru ssh. Would the file have been tagged if I had created it with OEDIT?

    There should probably be a notation in the doc about this....

    THANKS!

    ------------------------------
    Bill Seubert
    Solutions Architect
    AWS
    ------------------------------



  • 6.  RE: Error after customizing .profile and .bashrc for miniconda install

    ROCKETEER
    Posted 28 days ago
    Bill,

    OEDIT can tag files when you choose ASCII or UTF-8 on the Edit Entry panel. However, it sets a 'mixed encoding' tag, which is treated just like 'untagged' by bash. I'd recommend to avoid mixed-encoding tags in general. Untagged or mixed-tag ASCII is not going to work.

    If you leave ASCII/UTF-8 switch unset, OEDIT creates an untagged file with EBCDIC contents. This combination is perfectly normal for bash scripts, as well as for many other uses. That is, you can use OEDIT to create a bash script (including .bashrc) but in this case, do not select ASCII.


    If you're editing an existing file, OEDIT honors and preserves file's tag.

    Regards,
    Vladimir

    ------------------------------
    Vladimir Ein
    Rocket Software
    ------------------------------