Jay,

Here are some examples:

CU3958 write_smf_record: entered with type -2.
CU2086 write_smfTable_record_119: entered with table index 1.
CU1865 subtype_103: entered
CU1924 build_security_section: entered
GU5348 ftpSetApplData: entered

The messages are probably are meant for FTP developer use when diagnosing
an ftp customer issue, but IMO they should be documented somewhere for
customer reference. Once IBM documented the -d switch, I think the
debugging messages should have been documented also.

Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.

On Mon, Oct 7, 2024, 3:53 PM Jay Maynard <
[email protected]> wrote:

> What's the rest of the message?
>
> On Mon, Oct 7, 2024 at 2:30 PM Mike Shaw <[email protected]> wrote:
>
> > When executing FTP in batch on z/OS V2R5 with the '-d' option in the JCL
> > PARM= field:
> >
> > PARM='sitename.com -d (TIMEOUT 720'
> >
> > we see a LOT of messages issued with message numbers that I can't find
> > anywhere in any IBM doc. Examples are:
> >
> > GV0792
> > MV0519
> > MF0905
> > MV0754
> > MV0756
> > CG3169
> > CG3171
> > CG3183
> > CZ1374
> > CZ1459
> > CZ1459
> >
> > They all have that two-character alpha prefix followed by four numerics.
> >
> > Anyone know where these are documented? They are not defined in any IBM
> > message manual that I can find...
> >
> > Mike Shaw
> > MVS/QuickRef Support Group
> > Chicago-Soft, Ltd.
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
> >
>
>
> --
> Jay Maynard
>
> ----------------------------------------------------------------------
> 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

Reply via email to