Breadth-first and depth-first searches
Welcome to the Code Review Community.
General Observations
The use of small functions is very good and makes the code more readable, but overall the readability can be improved.
The code does seem to follow the concept of the single responsibility principle.
I'm going to address the code in 2 phases, one is dealing with improving the use of C programming and the second is coding style in general.
The use of structures to represent the queues and the stacks might have decreased the complexity of the code.
For the future it might be good if you provided an example input and expected output.
C Programming Improvements
Check for Warnings
When you initially compile with C use the -Wall compiler flag to list any warnings as well as any errors. In many cases the warnings can indicate possible bugs in the code.
While this code compiles it does have the following warnings using the -Wall flag:
gcc -Wall dfsbfs.c
dfsbfs.c:133:6: warning: return type of ‘main’ is not ‘int’ [-Wmain]
  133 | void main(){
      |      ^~~~
dfsbfs.c: In function ‘main’:
dfsbfs.c:138:14: warning: format ‘%s’ expects argument of type ‘char *’, but argument 2 has type ‘char (*)[10]’ [-Wformat=]
  138 |      scanf(&quot;%s&quot;,&amp;v);
      |             ~^  ~~
      |              |  |
      |              |  char (*)[10]
      |              char *
dfsbfs.c: In function ‘dequeue’:
dfsbfs.c:22:1: warning: control reaches end of non-void function [-Wreturn-type]
   22 | }
      | ^
dfsbfs.c: In function ‘POP’:
dfsbfs.c:87:1: warning: control reaches end of non-void function [-Wreturn-type]
   87 | }
      | ^

The warning about control reaches end of non-void function indicates that the code is missing a return statement if F == -1 in the function dequeue().
The warning about main () indicates that this program is not following the C programming standards about the main() function which should always return an integer value indicating the success or failure of the program to the operating system.
Avoid Global Variables
It is very difficult to read, write, debug and maintain programs that use global variables. Global variables can be modified by any function within the program and therefore require each function to be examined before making changes in the code. In C and C++ global variables impact the namespace and they can cause linking errors if they are defined in multiple files. The answers in this stackoverflow question provide a fuller explanation.
Magic Numbers
There are many Magic Numbers in the global declarations (-1, 10, 100 and 9), it might be better to create symbolic constants for them to make the code more readable and easier to maintain. These numbers may be used in many places and being able to change them by editing only one line makes maintenance easier.
Numeric constants in code are sometimes referred to as Magic Numbers, because there is no obvious meaning for them. There is a discussion of this on stackoverflow.
Readability and Coding Style
Code Consistency
The indentation of the code is inconsistent. This makes the code much harder to read and maintain. For instance it would be better if the function dequeue() looked something like this:
int dequeue(){
  if (F == -1)
  {
    printf(&quot;underflow\n&quot;);
  }
  else{
    vertex = q[F];
    printf(&quot;%c&quot;, vertex);
    F++;
    if (F &lt; 10)
    {
      return pos[F];
    }
    else
    {
      return -1;
    }
  }
}

Some other inconsistencies are that variables are both upper and lower case characters and in most cases are single characters while in some other cases meaningful names. In the C programming language some common practices are that variable and function names are all lower case, and that variable and functions names with multiple words are snake_case. Symbolic constants, which are not used in this program are all upper case.
Horizontal and Vertical Spacing
In most programming languages it is common to improve readability by using horizontal spacing between operators and operands as shown above in the if statements and the printf statements.
The code might be slightly more readable of the open braces { lined up with the closing braces '}', however, this would be determined by local coding standards.