Quantcast
Channel: IBM Mainframe Computers Forums
Viewing all 8500 articles
Browse latest View live

JCL & VSAM :: RE: FTP - JCL failed while passing FTP commands in dataset

$
0
0
Author: Robert Sample
Posted: Wed Nov 16, 2016 8:13 pm (GMT 5.5)

First, the 696 step condition code is 99000 modulo 4096 (which is the standard way z/OS handles codes larger than 4095). So telling us what it is doesn't add anything to the information already available.

Second, the error code 12 looks to be FTP_INPUT_ERR -- error reading INPUT or STDIN. Is there any chance that the FTP commands were edited and line numbers are in columns 73 through 80? If so, you'll need to remove them as FTP does NOT recognize line numbers in its subcommands. In my experience, this is the most common cause of input problems with FTP subcommands.

Third, you didn't bother to tell us what the step condition code nor the FTP output is for the step with the DELETE FILENAME.txt -- if you cannot provide complete information, that makes it much harder for us to help you.
_________________
TANSTAAFL

The first rule of code reuse is that the code needs to be worth re-using.

"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth


IMS DB/DC :: RE: IMS Database backup info

$
0
0
Author: ashek15
Posted: Wed Nov 16, 2016 11:37 pm (GMT 5.5)

Hi Enrico, Peter

Thanks for suggestions! Is there a way to query RECON datasets to gather backup info? Thanks
_________________
I am a DB2 DBA

IMS DB/DC :: RE: IMS Database backup info

$
0
0
Author: enrico-sorichetti
Subject: Reply to: IMS Database backup info
Posted: Thu Nov 17, 2016 2:00 am (GMT 5.5)

Quote:
Is there a way to query RECON datasets to gather backup info? Thanks


why not take a look at the manual Yourself ?
_________________
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort icon_cool.gif

IMS DB/DC :: RE: IMS Database backup info

$
0
0
Author: ashek15
Subject: Reply to: IMS Database backup info
Posted: Thu Nov 17, 2016 2:46 am (GMT 5.5)

Enrico - Thanks for your reply. I already searched manuals before putting this post, but could not find anything. That's why posted the query.
_________________
I am a DB2 DBA

JCL & VSAM :: RE: FTP - JCL failed while passing FTP commands in dataset

$
0
0
Author: Suneetha1612
Posted: Thu Nov 17, 2016 7:24 am (GMT 5.5)

Hi... Thanks for your reply.

I have checked the the data in file. There are no edited and line numbers from 73 to 80.

My Job is having 2 steps... as mentioned erlier. And i think I have provided the complete info.. If not please let me know.

Thank you.
_________________
Suneetha.P

JCL & VSAM :: RE: FTP - JCL failed while passing FTP commands in dataset

$
0
0
Author: Robert Sample
Posted: Thu Nov 17, 2016 7:36 am (GMT 5.5)

Quote:
And i think I have provided the complete info
You have not shown us:
- the JCL you are using
- the output of the first step
- the output of the entire job where the DELETE has been replaced with whatever command(s) you say do work
- a print of the &TEMP1 data set

You also have not told us what kind of server you are connecting to -- z/OS, z/OS Unix System Services, Windows, or Unix/Linux machine. So you have not provided anywhere near complete information.

Quote:
using FTPWEB PROC if only STEP1 is succesful
In case you are not aware of it, FTPWEB is specific to your site -- it is NOT a generally used procedure; I've never heard of it before today despite many years of using FTP.

Looking at what you HAVE provided, there are indications that your &TEMP1 data set has a problem -- the EZA1460I prompt is usually followed by the first command in the input data set. It could be that &TEMP1 is associated with the wrong DD name, or there could be some other problem.
_________________
TANSTAAFL

The first rule of code reuse is that the code needs to be worth re-using.

"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth

IMS DB/DC :: RE: IMS Database backup info

$
0
0
Author: PeterHolland
Posted: Thu Nov 17, 2016 10:27 am (GMT 5.5)

There are LIST RECON commands. Documented in the manuals.

The RECON contains info about image copy datasets, but no info about failed image copy runs. This is also described in the manuals.

JCL & VSAM :: RE: FTP - JCL failed while passing FTP commands in dataset

$
0
0
Author: Suneetha1612
Posted: Thu Nov 17, 2016 11:50 am (GMT 5.5)

Hi

My JCL is
Code:
---------------------------------------------------------------------------
//STEP2    EXEC SAS,COND=(0000,NE)               
//SYSPRINT DD SYSOUT=*                           
//SYSOUT   DD SYSOUT=*                           
//SYSUDUMP DD SYSOUT=*                           
//SYSSNAP  DD SYSOUT=*                           
//SYSTERM  DD SYSOUT=*                           
//DASA     DD DSN=USERID.WORKPACK.SS1,DISP=SHR
//DASB     DD DSN=USERID.WORKPACK.SS2,DISP=SHR
DATA FTPREC(KEEP=FTPIN FTPOUT FTPOPT FTPMSK);
  INFILE DASA END=LASTOBS;                   
      INPUT @1    FTP_REC               $100.
        ;                                     
DATA DASB(KEEP=FTPINP);                 
  LENGTH FTPINP $70.;                   
  SET FTPREC;                           
  IN_PATH1 = 'CD  \PATH1\PATH2\';         
  IN_PATH2 = 'DIR';                     
  IN_PATH3 = 'DELETE' || FTPREC;                     
  IN_PATH4 = 'DIR';                     
  IN_PATH5 = 'QUIT';                     
  IF _N_ = 1 THEN DO;                   
    FTPINP = IN_PATH1;                   
    OUTPUT;                             
  END;                                   
  DO I = 2 TO 5;                         
    IF I = 2 THEN FTPINP = IN_PATH2;     
    IF I = 3 THEN FTPINP = IN_PATH3;     
    IF I = 4 THEN FTPINP = IN_PATH4;     
    ELSE IF I = 5 THEN FTPINP = IN_PATH5;
    OUTPUT;           
  END;               
 DATA _NULL_;             
   SET DASB;             
   FILE DASB;           
   PUT @1   FTPINP   $70.
       ;                             
 RUN;       
//**************** PROGRAM NAME : FTPWEB ****************       
//STEP2    EXEC FTPWEB,PARM='(EXIT'       
//SYSPRINT DD SYSOUT=*                                           
//SYSOUT   DD SYSOUT=*                                           
//SYSUDUMP DD SYSOUT=*                                           
//SYMMFAP  DD SYSOUT=*                                           
//SYSTERM  DD SYSOUT=*                                           
//INPUT    DD DSN=USEDID.CNTL(SIGNON),DISP=SHR
//         DD DDNAME=SYSIN                                       
//OUTPUT   DD SYSOUT=*                                                     
//SYSIN    DD DSN=USERID.WORKPACK.SS2,DISP=SHR

-------------------------------------------------------------------------------
Output of STEP1 is a dataset with FTP commands to be executed in next step.
Quote:
- a print of the &TEMP1 data set

Code:

CD \PATH1\PATH2\
DIR
DELETE FILENAME.txt
DIR
QUIT

----------------------------------------------------------------------
Quote:
- the output of the entire job where the DELETE has been replaced with whatever command(s) you say do work


Code:
EZA1789I PASSWORD:                                   
EZA1701I >>> PASS                                   
230 User logged in.                                 
EZA1460I Command:                                   
EZA1735I Std Return Code = 99000, Error Code = 00012
EZA1701I >>> QUIT                                   
221 Goodbye.                                         

STEP2 - STEP WAS EXECUTED - COND CODE 0696


Please let me know if I am missing something... Dont know where it went wrong
_________________
Suneetha.P


JCL & VSAM :: RE: FTP - JCL failed while passing FTP commands in dataset

$
0
0
Author: Bill Woodger
Subject: Reply to: FTP - JCL failed while passing FTP commands in dataset
Posted: Thu Nov 17, 2016 12:27 pm (GMT 5.5)

You have no explicit SYSIN DD for your SAS step.

You have no evidence in what you have shown of the existence of an actual &TEMP1 data set, so at the moment printing its contents is useless.

You use two different DDs to read (on one) and update (on another) the same dataset. This is an incredibly bad idea, which you may be getting away with simply because the data set contains only a small number of records. Don't do that.

Note also that you are updating with DISP=SHR, which means that if you submit your JOB twice, both JOBs can execute at the same time, further increasing the chance of corruption.

Note also also, that if you SAS fails for any reason, you may well corrupt your input data set with your output data set. If you want to do "corrupt-in-place" processing (same data set for input and output, non PDS/PDSE) then you must do a backup before the step.

You haven't provided DCB info for the data set.

When you enter the alleged instructions by hand, do they work? Enter them by hand into a data set with the same characteristics and experiment (editor) to make them not work.

DB2 :: Db2 SQL query to convert rows into columns

$
0
0
Author: subratarec
Subject: Db2 SQL query to convert rows into columns
Posted: Thu Nov 17, 2016 4:51 pm (GMT 5.5)

Hi All,

Need your help/suggestion on below query. Could someone please share his/her thought on how to create below query..

Table Name: My_Dept

Db2 Table
--------------------------------------------
Code:
Emp_Name | Dept_name
-----------------------------
AAAA     | Math
-----------------------------
BBBB     | Math
-----------------------------
CCCC     | Physics
-----------------------------
DDDD     | Chemistry
-----------------------------
EEEE     | Physics
-----------------------------
FFFF     |  Physics     

output of query result..


Code:
Math | Physics | Chemistry
------------------------------
AAAA |           |
------------------------------
BBBB |           |
------------------------------
     | CCCC      |
------------------------------
     | EEEE      |
------------------------------
     | FFFF      |
------------------------------
     |           | DDDD


Thanks

DB2 :: RE: Db2 SQL query to convert rows into columns

$
0
0
Author: Nic Clouston
Posted: Thu Nov 17, 2016 7:04 pm (GMT 5.5)

This same question has been asked on the beginners forum, I suggest yoou go there and follow that topic. To get there, if you do not already know it, use the Protal link at the top of every page in ths forum and on the left there is a section for beginners with 3 links including a link to that forum.

If that was your topic then posting again on this forum is a waste of everyones time and is bad internet manners.
_________________
Regards
Nic

DB2 :: RE: Db2 SQL query to convert rows into columns

$
0
0
Author: Marso
Posted: Thu Nov 17, 2016 7:17 pm (GMT 5.5)

If the number of "Dept_name" is fixed and known, then you could write:
Code:
SELECT                               
   CASE DEPT_NAME
      WHEN 'Math' THEN Emp_Name
      ELSE ' '                       
   END AS MATH,                               
   CASE DEPT_NAME
      WHEN 'Physics' THEN Emp_Name
      ELSE ' '                       
   END AS PHYSICS,                               
   CASE DEPT_NAME
      WHEN 'Chemistry' THEN Emp_Name
      ELSE ' '                       
   END as CHEMISTRY                               
FROM                                 
   My_Dept
ORDER BY
   DEPT_NAME

However, this kind of coding is absolutely not recommended: a new department would requires changes in the query.

JCL & VSAM :: RE: FTP - JCL failed while passing FTP commands in dataset

$
0
0
Author: Robert Sample
Posted: Thu Nov 17, 2016 7:37 pm (GMT 5.5)

It is possible that USERID.CNTL(SIGNON) is causing your problem; since you didn't list it, who knows? What is the LRECL of USERID.CNTL? What is the LRECL of USERID.WORKPACK.SS2?

Your SAS code is incredibly bad. Why not simplify it to
Code:
DATA DASB(KEEP=FTPINP);                 
   SET FTPREC;                           
   FILE DASB ;
   PUT 'CD  \PATH1\PATH2\';         
   PUT 'DIR';                     
   PUT 'DELETE ' FTPREC $63.;                     
   PUT 'DIR';                     
   PUT 'QUIT';                     

Furthermore, you STILL have not shown us any job output of a completely successful run as you claimed in your original post:
Quote:
I used to run similar job through PUT and GET commands. And they are successful.
Unless you can show us the successful job, executed in precisely the same manner as you did in the posted job, your claim to have a successful execution is, to say the least, suspect. And to echo Bill's comment, your original post talked about an &TEMP1 data set -- yet the posted JCL does not have this. Either you are not posting what you are using, or you are posting about things you are not doing in your JCL.

Since you cannot clearly and simply post what you are doing, what your results are, and how your results are different from what you want, why should this topic not be locked as a complete waste of time?
_________________
TANSTAAFL

The first rule of code reuse is that the code needs to be worth re-using.

"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth

DFSORT/ICETOOL :: Convert +9999999999999.99 to S9(12)V9(3)

$
0
0
Author: vnktrrd
Subject: Convert +9999999999999.99 to S9(12)V9(3)
Posted: Thu Nov 17, 2016 8:15 pm (GMT 5.5)

Hi,

I have a value like +9999999999999.99 which I want to convert to S9(12)V9(3).

After the conversion it should like 99999999999999{

Please advise how to achieve this using DFSORT.

Thanks,
Ramana.

DFSORT/ICETOOL :: RE: Convert +9999999999999.99 to S9(12)V9(3)

$
0
0
Author: Arun Raj
Posted: Thu Nov 17, 2016 8:21 pm (GMT 5.5)

You have 13 9s before the decimal point in the example and you want to read it with 9(12)?. Anyways look here for examples on SFF format.
_________________
Arun
----------------------------------------------------------------------------------------------------
Love is like an hourglass, with the heart filling up as the brain empties. -Jules Renard


DFSORT/ICETOOL :: RE: Convert +9999999999999.99 to S9(12)V9(3)

$
0
0
Author: Bill Woodger
Subject: Reply to: Convert +9999999999999.99 to S9(12)V9(3)
Posted: Thu Nov 17, 2016 9:43 pm (GMT 5.5)

If that is your data, you can just hard-code the PD value.

Since that is unlikely, what do other examples of that data look like? Is the position fixed? Length fixed? Sign fixed? Always two decimals? We can't tell much from one piece of example data.

DB2 :: RE: Db2 SQL query to convert rows into columns

$
0
0
Author: Rohit Umarjikar
Posted: Thu Nov 17, 2016 10:06 pm (GMT 5.5)

Quote:
However, this kind of coding is absolutely not recommended: a new department would requires changes in the query.
This is the optimal solution which needs minimal change.
_________________
Regards,
Rohit Umarjikar
"Knowledge is knowing that a tomato is a fruit, but Wisdom is knowing not to put it in a fruit salad."icon_razz.gif

DFSORT/ICETOOL :: RE: Convert +9999999999999.99 to S9(12)V9(3)

$
0
0
Author: vnktrrd
Subject: Reply to: Convert +9999999999999.99 to S9(12)V9(3)
Posted: Thu Nov 17, 2016 10:17 pm (GMT 5.5)

Hi Bill,

Yes the data is fixed except for the sign which may be + or - . I have to retain the sign always.

I have tried with the below OUTREC but I am not getting the expected output.

Code:

OUTREC BUILD=(1,17,SFF,TO=ZD,LENGTH=15)


Input :
-0000037723069.39
Output :
00000377230693R

and when I move this value to S9(12)V9(3) it is being stored as 3772306.93 instead of 37723069.39.

Thanks,
Ramana.

DFSORT/ICETOOL :: RE: Convert +9999999999999.99 to S9(12)V9(3)

$
0
0
Author: Bill Woodger
Subject: Reply to: Convert +9999999999999.99 to S9(12)V9(3)
Posted: Thu Nov 17, 2016 10:33 pm (GMT 5.5)

How do you define the field you MOVE to the S9(12)V9(3)? Your BUILD is working, bearing in mind that you don't have three decimal places in your data. I

DFSORT/ICETOOL :: RE: Convert +9999999999999.99 to S9(12)V9(3)

$
0
0
Author: vnktrrd
Subject: Reply to: Convert +9999999999999.99 to S9(12)V9(3)
Posted: Thu Nov 17, 2016 10:34 pm (GMT 5.5)

with hex on it looks like below.


Code:

FFFFFFFFFFFFFFD
000003772306939
[/code]
Viewing all 8500 articles
Browse latest View live