IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Connect Direct 6.3 for Z/OS


IBM Mainframe Forums -> All Other Mainframe Topics
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Sun Nov 26, 2023 10:20 pm
Reply with quote

Hi,
I'm upgrading connect direct Z/OS to 6.3. When try to start th starter task, the Highwater erorr message appear as follows:

SITA386E SESSION.HIGHWATER.SMF records are not being recorded - SMFRTEST RC= 36

I check /D SMF,O and type 133 is one of the SMF record. Any guide?


Thanks
Regards
Netcrawler
Back to top
View user's profile Send private message
Joerg.Findeisen

Senior Member


Joined: 15 Aug 2015
Posts: 1295
Location: Bamberg, Germany

PostPosted: Mon Nov 27, 2023 6:56 am
Reply with quote

See https://www.ibm.com/docs/en/connect-direct/6.3.0?topic=parameters-sessionhighwatersmf-133-128-255-1-60-no
Back to top
View user's profile Send private message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Mon Nov 27, 2023 9:01 am
Reply with quote

Hi Joerg,

We have followed this link and not supress record type 133 but the same message still appears. We are using X11 and unable to set the parameter to 'NO'. The display odf our SMF as below:

/D SMF,O

SYS(EXITS(IEFACTRT)) -- PARMLIB
SYS(TYPE(0,2,3,6:10,14,15,22:24,26,30,32,33,41,42,47:48,59,
60:69,70:79,80:83,85,88,89,90:91,94,98,100:103,108,110,111,
113,115:117,130,133,134,148:151,161,200,244,245)) -- PARMLIB
SYNCVAL(15) -- PARMLIB
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1743
Location: Tirupur, India

PostPosted: Mon Nov 27, 2023 6:14 pm
Reply with quote

SMF record type values are customizable, but by default,

watsonwalker.com/wp-content/uploads/2020/11/SMF-Reference-20201107.pdf
132 : IBM Sterling Connect:Direct for z/OS Statistics Exit
133 : IBM Sterling Connect:Direct for z/OS

You already have 133 in the SMFPRMXX, it is possible that Connect Direct requires 132 as well. Worth a shot. Can you include 132 in the SMFPRMXX.

Given that you are upgrading and not installing it afresh, this error should have appeared in previous version as well. Is there any chance you enabled Statistics exit during the upgrade?
Back to top
View user's profile Send private message
Pedro

Global Moderator


Joined: 01 Sep 2006
Posts: 2569
Location: Silicon Valley

PostPosted: Tue Nov 28, 2023 2:26 am
Reply with quote

Are there any other messages produced when you try to start it?
Back to top
View user's profile Send private message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Tue Nov 28, 2023 10:11 am
Reply with quote

Hi VasanthZ,

We are using V5.02 and the Highwater is not a compulsory in this version. How to check if 133 already been used? Will try 132 later. tks

Hi Pedro,

Not other message except the highwater message.
Back to top
View user's profile Send private message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Tue Nov 28, 2023 2:20 pm
Reply with quote

We got another message SITA997I Security Environment Invalid for Connect:Direct.. Is this link to SITA386E SESSION.HIGHWATER.SMF records are not being recorded?
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 584
Location: London

PostPosted: Tue Nov 28, 2023 3:34 pm
Reply with quote

SITA997I

MODULE: DMINIT2

Security Environment Invalid for Connect:Direct.
Connect:Direct is running in a RACF Program Control
environment, but the JOBLIB/STEPLIB/LINKLIB DSNs from which Cicon_biggrin.gif
modules were fetched are not in the Program Control list.

Either turn off Program Control, or place all the
JOBLIB/STEPLIB/LINKLIB DSNs in the appropriate RACF table.
Back to top
View user's profile Send private message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Thu Nov 30, 2023 3:40 pm
Reply with quote

After we add in all JOBLIB/STEPLIB/LINKLIB DSNs in the appropriate RACF table. the problem resolved. Now another problem with below messages:

SITA121I Keyword not Specified in INITPARMS: AUTHDSN
SITA121I Keyword not Specified in INITPARMS: CKPTDSN
SITA121I Keyword not Specified in INITPARMS: MSGDSN
SITA121I Keyword not Specified in INITPARMS: NETDSN
SITA121I Keyword not Specified in INITPARMS: TYPEDSN
SITA123I REQUIRED initparm is not set, terminating.


How to resolve this problem ? Any idea?
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 584
Location: London

PostPosted: Thu Nov 30, 2023 3:47 pm
Reply with quote

If you have the ConnectDirect product licensed then you should have access to the manual. Whatever the parmlib is in the started task JCL obviously needs these parm's added, and the manual should explain the syntax and meaning of each one.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 584
Location: London

PostPosted: Thu Nov 30, 2023 4:27 pm
Reply with quote

On the EXEC in the C : D started task proc it has
PARM=('DSN.PARMLIB(MEMBER))','&PRM')

In that parmlib member you specify the dataset names that relate to each keyword where DSN below is whatever your
C : D set up uses for the HLQ etc, probably the same HLQ as names specified on the DMPUBLIB and ONLYONE DDnames in the STC proc. Just find the names of the datasets with the correct suffix to match the keyword


KEYWORD DSN
--------- ------------------------------
AUTHDSN = DSN.AUTH
CKPTDSN = DSN.CKPT
MSGDSN = DSN.MSG
NETDSN = DSN.NETMAP
STAT.ARCH.DIR = DSN.STATS.ARCHDIR
STAT.DSN.BASE = DSN.STATS
TYPEDSN = DSN.TYPE
SECURE.DSN = DSN.PFILE
Back to top
View user's profile Send private message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Sat Dec 02, 2023 11:01 pm
Reply with quote

We have put exact HLQ for the VSAM files similar to DMPLIB and linklib SYS3.CDZ.V63.SDGAPROC & SYS3.CDZ.V63.SDGALINK
i.e

CKPTDSN = SYS3.CDZ.V63.CKPT
MSGDSN = SYS3.CDZ.V63.MSG
NETDSN = SYS3.CDZ.V63.NETMAP
STAT.ARCH.DIR = SYS3.CDZ.V63.STATS.ARCHDIR
STAT.DSN.BASE = SYS3.CDZ.V63.STATS
TYPEDSN = SYS3.CDZ.V63.TYPE

However, we still having same messages. Just wonder PGM=DGADINIT unable to recognise the keyword for the initparm. Should we maintain any other libraries in CLIST or Linklib?
Back to top
View user's profile Send private message
Pedro

Global Moderator


Joined: 01 Sep 2006
Posts: 2569
Location: Silicon Valley

PostPosted: Sun Dec 03, 2023 1:29 am
Reply with quote

re: Not other message except the highwater message.

followed by: We got another message SITA997I Security Environment...

Hilarious!
Back to top
View user's profile Send private message
Pedro

Global Moderator


Joined: 01 Sep 2006
Posts: 2569
Location: Silicon Valley

PostPosted: Sun Dec 03, 2023 1:34 am
Reply with quote

re: "We have put exact HLQ for the VSAM files"

Please show us your entire JCL from proclib.

update: instead of using proclib, try to run from a batch job so that you can show us the entire job output files.
Back to top
View user's profile Send private message
Pedro

Global Moderator


Joined: 01 Sep 2006
Posts: 2569
Location: Silicon Valley

PostPosted: Sun Dec 03, 2023 1:44 am
Reply with quote

Per the documentation, it seems that you can use an ISPF customization process that will produce your JCL in DGAJNETL. Did you follow that process?
Back to top
View user's profile Send private message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Mon Dec 04, 2023 1:59 pm
Reply with quote

Hi, managed to resolved the problem as we took the initparm from V5.2 and changed according to V6.3 datasets/VSAM file for V6.3. We were able to start the CD server/Starter task, but got message as below:

SITA523I RPLERRCK INITIALIZED
U0008 13:38:57.71 STCO114I TCP/IP BIND Failed for address 1364;172.24.3.20
U0008 13:38:57.71 STCO999E FUNCTION=BIND RETURN CODE=0000006F TEXT=EACCES: Permission is denied
U0008 13:38:57.71 STCO999E FUNCTION=BIND REASON CODE=744C7246 TEXT=Action: Specify a valid port.


My starter task is ACCDZ63T and We believed the ACCDZ63T should be granted some permission to the TCP but we just can't indentify what to be granted? Anyone got idea? If we renamed the starter task to our old V5.2 starter task name, we were able to start the CD server 6.3.
Back to top
View user's profile Send private message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Tue Dec 05, 2023 12:58 pm
Reply with quote

Manage to bring up the starter task after define the port 1364 for ACCDZ63T. Now. We are able to bring up CD Server/Starter Task.
However, noticte an error message for MSG file during initialization:

SITA067I MESSAGE file is open.
13.33.33 STC72840 SMSG008I GET FOR MSGFILE FAILED. RC=00000008 FEEDBACK=00000010 976
976 SMSG008I KEY=SITA760W(X'E2C9E3C1F7F6F0E6')

Any idea how to resolve the error?
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 584
Location: London

PostPosted: Tue Dec 05, 2023 1:42 pm
Reply with quote

What was the status of the MSGFILE when you started the STC? Was it empty, or already populated with some data? It may be finding a duplicate key. or needs initialising if empty. We can't determine this remotely so ask for local site support.

SMSG008I

MODULE =DMGMSGFH

GET FOR MSGFILE FAILED. RC=rr FEEDBACK=fdbk KEY=msgid
A GET request from the Connect:Direct message file failed. The
VSAM return code from a SHOWCB and FDBK code are displayed.
The message ID being looked up is also shown.

SYSTEM ACTION : This message is displayed to the ESTAE DD also.
A return code of 8 is passed back to the module who called
the message file handler. If RC=8 and FDBK=16, an "not found"
indicator is set in the caller's PLIST
RESPONSE: Gather the output from the ESTAE DD and the system
log. Look up the system log messages in the IBM manuals and
determine what action to take. If unable to ascertain an action
contact IBM Support after gathering the log and ESTAE DD output
Back to top
View user's profile Send private message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Wed Dec 20, 2023 8:55 am
Reply with quote

After we redefined the MSG file we managed to bring up the CD server/Starter TASK. As we are running 5655-X11 the HIGHWATER.SMF messages keep coming out from the starter task log. Fyi, we comment off the HIGHWATER.SMF for initparm,otherwise the starter would not able to be started giving errror

SITA386E SESSION.HIGHWATER.SMF records are not being recorded - SMFRTEST RC=36

Anyone have encountered similar problem? Although we have defined the Rec TYPE = 133 in SMF as advised by IBM, but the problem still persist.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 584
Location: London

PostPosted: Wed Dec 20, 2023 11:20 am
Reply with quote

This very site specific so you need to talk to your local System Programmers. Your SMF type 133 may be suppressed for some reason, perhaps it's used by another product. We can't determine that. Below is an excerpt from the manual and the D SMF command they advise to use would be a good start to see if TYPE 133 is actually suppressed.

SESSION.HIGHWATER.SMF = (133 | 128-255, 1-60) | NO
Last Updated: 2023-01-25
This parameter determines the SMF record type number and the recording interval for High Water Mark records. For License permitting the acceptable range is (133 | 128-255, 1-60). The default value is (133 , 60) where the second value is in minutes.

If the SMF record id of 133 is being used by other applications, you must specify a suitable record id with this initialization parameter. The value of NO is only valid for license versions X01 and X12. X09 and X11 licenses require the SESSION.HIGHWATER.SMF parameter.
If message SITA386E or SITA386W appears, it means the default or specified record type is being suppressed by SMF. Refer to D SMF, O display and look for NOTYPE sub parameter of the SYS parameter to see which records are being suppressed.
Back to top
View user's profile Send private message
netcrawler

New User


Joined: 31 Mar 2008
Posts: 29
Location: Kuala Lumpur

PostPosted: Wed Dec 20, 2023 1:26 pm
Reply with quote

Hi Pete,

I have talked to our system programmer and IBM Support but they still have no idea why these messages keep coming out. We didn't suppress TYPE=133 as you could see my D SMF, O display as follows:

SUBSYS(JES2,TYPE(0,2,3,6:10,14,15,22:24,26,30,32,33,41,42,
47:48,59,60:69,70:79,80:83,85,88,89,90:91,94,98,100:103,108,
110,111,113,115:117,130,132,133,134,148:151,161,200,244,245))



SYS(EXITS(IEFACTRT)) -- PARMLIB
SYS(TYPE(0,2,3,6:10,14,15,22:24,26,30,32,33,41,42,47:48,59,
60:69,70:79,80:83,85,88,89,90:91,94,98,100:103,108,110,111,
113,115:117,130,132,133,134,148:151,161,200,244,245)) --
PARMLIB
SYNCVAL(15) -- PARMLIB


I tried 132 also failed with same message:

SITA386E SESSION.HIGHWATER.SMF records are not being recorded - SMFRTEST RC=36
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> All Other Mainframe Topics

 


Similar Topics
Topic Forum Replies
No new posts Getting TWA in CICS program while con... CICS 14
No new posts Unable to connect FTP over TLS from z... All Other Mainframe Topics 5
No new posts Connect:Direct Add yesterday date in ... All Other Mainframe Topics 3
No new posts FTP - connect with certificate, no pa... JCL & VSAM 1
No new posts ZOS Connect EE Vs z/OS client web ena... All Other Mainframe Topics 4
Search our Forums:

Back to Top