At this time, we are running parallel tests against our production jobs to find differences between PRODUCTION (NAT232, ADA742) and DEVELOPMENT (NAT413, ADA742), before upgrading PROD to NAT413.

Job A is writing ET data and job B is reading the same ET data. Production (NAT232) is working fine.

In DEVL (NAT413) job B cannot read the ET data because it was written under the jobname instead the ETID, which is supported in NSC. The library has also the 'RESTART=Y' flag in NSC.

Yes, we are running with the latest NAT413 version: ZAP level 3175, Service Pack 3 for NAT and NSC. SAG request #573230 is still open.

It seems to me, at this time, that NSC in batch is the point. Some users receive the value of ETID from NSC, and others receive the *INIT-USER (jobname), even if ETID is supported in NSC. And we don't have ET-data problems when we start online programs.

To test this, I wrote the following two little programs:

WRIT-ET:
0010 	DEFINE DATA LOCAL                                                
0020 	1 #ET-DATA (A70)                                                 
0030 	1 #ENV     (A06)                                                 
0040 	END-DEFINE                                                       
0050 	IF *DEVICE = 'BATCH  '                                           
0060 	  #ENV := 'batch'                                                
0070 	ELSE                                                             
0080 	  #ENV := 'online'                                               
0090 	END-IF                                                           
0100 	COMPRESS  'Dieter Storr was here' *DATN *TIMN #ENV INTO #ET-DATA 
0110 	END TRANSACTION #ET-DATA                                         
0120 	END     
                                                         
READ-ET:
0010 	DEFINE DATA LOCAL             
0020 	1 #ET-DATA (A70)              
0030 	END-DEFINE                    
0040 	GET TRANSACTION DATA #ET-DATA 
0050 	WRITE #ET-DATA                
0060 	END  

Natural Security:
NSC USER = USER01, ETID=DIETER
NSC USER = BAT4100, ETID=BAT4100
NSC LIBRARY = LIB1, RESTART=Y    

And the batch job:
000001 //USER01ET JOB (IT,DBA),.....
(snip)
000007 //WRITEET  EXEC NATBATCH   
000008 //CMSYNIN  DD *            
000009 LIB1,USER01,PASSWORD       /* 2nd: LIB1,BAT4100,PASSWORD           
000010 WRIT-ET                    
000011 FIN                        
000012 //READET   EXEC NATBATCH   
000013 //CMSYNIN  DD *            
000014 LIB1,USER01,PASSWORD       /* 2nd: LIB1,BAT4100,PASSWORD              
000015 READ-ET                    
000016 FIN      

Output of batch job:
NEXT LOGON LIB1                  
Logon accepted to library LIB1.  
NEXT WRIT-ET                         
NEXT FIN       
                     
NEXT LOGON LIB1                                                            
Logon accepted to library LIB1.                                            
NEXT READ-ET                                                                   
Page      1                                         05-04-07  17:26:55 
Dieter Storr was here 20050407 1726542                                          
NEXT FIN          
                                                              
ADABAS Checkpoint File:
#  ET ID                        ET Data                           ISN   
-- --------  --------------------------------------------------  --------
1. DIETER    Dieter Storr was here 20050407 1726542 batch             214
2. USER01ET  Dieter Storr was here 20050407 1731366 batch             216


1. test with logon LIB1,USER01,PASSWORD   (ETID from NSC)
2. test with logon LIB1,BAT4100,PASSWORD  (ETID from jobname)             
                                                                                             

Status 12 April 2005: It seems that FSEC (NSC413) in one environment has problems. A test with NAT413 in production went OK. Checks using ADAACK, ADAICK, and ADAVAL went fine. SAG development is looking into this issue.

Top Page

Back to NATURAL Tips, Tricks, Techniques -- Overview