I think it's related. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Andrew Rowley Sent: יום ה 20 יולי 2023 14:05 To: [email protected] Subject: Re: Problem running GIMUNZIP job.
Maybe this problem? https://community.rocketsoftware.com/discussion/miniconda-conflicts-with-bpxbatch On 20/07/2023 8:10 pm, Gadi Ben-Avi wrote: > Hi, > I managed to find the problem. > My user was running a different shell which was causing the problem. > Once I reverted back to /bin/sh, everything started working. > > Gadi > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of Colin Paice > Sent: יום ה 20 יולי 2023 11:35 > To: [email protected] > Subject: Re: Problem running GIMUNZIP job. > > I do not see //SYSOUT or //SYSPRINT in your JCL... try adding them. > //SYSPRINT DD SYSOUT=* etc > You might try adding ECHO 'BLAH' to the script so you know something > will be displayed Colin > > On Thu, 20 Jul 2023 at 08:46, Gadi Ben-Avi <[email protected]> wrote: > >> Hi, >> We are in the process of installing z/OS v2.5 from z/OSMF. >> One of the first jobs uses GIMUNZIP to create the new z/OS libraries. >> When the job got to the SMPPTS library, we got these messages: >> GIM43501S ** THE CALL TO THE BPX1WRT SERVICE FAILED WHEN PROCESSING >> >> >> /tmp/izud-V110AVN-T1314651/unzip/smpe2023201100726173157/S0354.CB.S0354.CB.ST252475.SMPE.SMPPTS.pax.Z. >> THE RETURN >> CODE WAS '00000077'X AND THE REASON CODE WAS 'E3000029'X. >> GIM47800S ** AN ERROR OCCURRED WHILE GIMUNZIP WAS PROCESSING ARCHIVE >> ZSMSP9.CB.ST252475.SMPE.SMPPTS. >> GIM20501I GIMUNZIP PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS >> 12. >> >> Before the GIMUNZIP step, the job allocates a new ZFS and is supposed >> to mount it at /tmp/izud-V110AVN-T1314651/unzip, but from what I can >> see, this is does not happen, and the files are restores to /tmp, >> which does not have enough space. >> >> The job includes some shell scripts that are supposed to mount the >> ZFS, but it doesn't look like they are running. >> >> The step looks like: >> //MOUNT EXEC PGM=BPXBATCH,COND=(0,LT) >> //STDPARM DD * >> SH ; >> mpdir=/tmp/izud-V110AVN-T1314651/unzip; >> dsn='V110AVN.SWDEPL.T1314651.ZFS'; >> if -e "$mpdir" ¤; then; >> rm -r $mpdir; >> fi; >> if ! -e "$mpdir" ¤; then; >> echo "Work directory $mpdir will be created."; >> umask 077 ; >> mkdir -p -m 700 "$mpdir"; >> fi; >> PATH=$PATH:/usr/sbin; >> echo "Format the file system $dsn."; >> zfsadm format -aggregate $dsn; >> echo "Mount $dsn on $mpdir."; >> mount -s nosetuid -t ZFS -f $dsn $mpdir; >> >> There is no output in STDOUT or STDERR. >> >> How can I see the output of the script to make sure it is actually running? >> >> I would ask IBM, but this is running on z/OS v2.3, which is not >> supported, and they won't help. >> >> Thanks >> >> Gadi >> >> >> >> --------------------------------------------------------------------- >> - For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO >> IBM-MAIN >> > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN -- Andrew Rowley Black Hill Software ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
