needs clarification



IBM's Command List programming language & Restructured Extended Executor

needs clarification

Postby syamcs » Fri Mar 18, 2011 11:40 am

hi,
i just tried to automate the RACF command ADDUSER using REXX but showed an error "incorrect name syntax"

is it possible to use ADDUSER command using rexx?
Regards
Syam
syamcs
 
Posts: 56
Joined: Thu Feb 10, 2011 5:36 pm
Location: chennai
Has thanked: 0 time
Been thanked: 0 time

Re: needs clarification

 

Re: needs clarification

Postby mongan » Fri Mar 18, 2011 12:58 pm

why is the sky blue?
Please give us real information and error messages about your problem, then you can ask a question. From what you wrote I assume that the adduser name does not respect the racf syntax for the name.
User avatar
mongan
 
Posts: 212
Joined: Tue Jan 11, 2011 8:32 pm
Has thanked: 1 time
Been thanked: 5 times

Re: needs clarification

Postby syamcs » Fri Mar 18, 2011 2:01 pm

address tso "ADDUSER (DEMS) NAME('SYAM') PASSWORD(HELLO) DFLTGRP(APPL) OWNER(DUSR001) TSO(ACCTNUM(ACCT#) PROC(IKJDB2) SIZE(4096) MAXSIZE(8212)"

i am getting the following error

IKJ56621I INVALID COMMAND NAME SYNTAX
syamcs
 
Posts: 56
Joined: Thu Feb 10, 2011 5:36 pm
Location: chennai
Has thanked: 0 time
Been thanked: 0 time

Re: needs clarification

Postby NicC » Fri Mar 18, 2011 2:52 pm

ADDUSER is not a TSO command but you are passing it to TSO. It is a RACF command - RACF is not TSO.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: needs clarification

Postby steve-myers » Fri Mar 18, 2011 7:03 pm

NicC wrote:ADDUSER is not a TSO command but you are passing it to TSO. It is a RACF command - RACF is not TSO.

ADDUSER is a TSO command provided with the IBM RACF product. So you can say it is both a RACF command and a TSO command.

You get the IKJ56621I INVALID COMMAND NAME SYNTAX message if there is something wrong with the command name; 1234 entered as a TSO command will give this message. I suspect the real problem is elsewhere since I don't see anything obviously wrong with the ADDUSER command in the initial post. I have run the ADDUSER command in TSO CLISTs (I don't do Rexx) with no problem.
steve-myers
Global moderator
 
Posts: 1886
Joined: Thu Jun 03, 2010 6:21 pm
Has thanked: 4 times
Been thanked: 197 times

Re: needs clarification

Postby enrico-sorichetti » Fri Mar 18, 2011 7:14 pm

if the command is as posted a closing parenthesis is missing for the TSO parameter
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
enrico-sorichetti
Global moderator
 
Posts: 2644
Joined: Fri Apr 18, 2008 11:25 pm
Has thanked: 0 time
Been thanked: 130 times

Re: needs clarification

Postby NicC » Sat Mar 19, 2011 12:18 am

I stand corrected - further educated:)
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: needs clarification

Postby Pedro » Sat Mar 19, 2011 1:10 am

To say it a little bit differently...

Using Address TSO causes a search in the normal places for the named command (a load module, or even CLIST or REXX program). And for it to be called using a particular parameter convention.

Various products can be installed and their commands will work in TSO even though they are not provided by the TSO product. See TSO/E Programming Guide.
Pedro Vera
User avatar
Pedro
 
Posts: 569
Joined: Thu Jul 31, 2008 9:59 pm
Location: Silicon Valley
Has thanked: 0 time
Been thanked: 39 times


Return to CLIST & REXX

 


  • Related topics
    Replies
    Views
    Last post